Resources would be anything that is online. Almost anything that is connected to the Internet can be checked using our monitoring. You can monitor everything from a website to your home Internet. If it is connected it can generally be a resource.
For example, let's say you have a single website and you also want to make sure your home and office Internet are all up and running. Each one of these would count as one resource. In this scenario, you would get an instant notification not only if your website goes down but also if your Internet goes down.
Services are the additional programs and components that run on a resource. Consider your website, it isn't just an isolated entity but runs using a network of custom programs. You will have the power of instant notification, if the process stops working even even for things that can't normally be checked via online methods.
DevOps (people that maintain and work with server code) are a critical part of any business with resources they depend on that are online. The biggest problem is that in-house staff is really expensive and the costs don't pay off until an emergency happens. So what do most companies do when everything seems to go wrong? They higher extremely overpriced teams that can only help you get the service back on not getting it working again. This results in hours if not days worth of downtime. Our DevOps team is obsessed with your uptime and will make sure that any of your resources either local, hosted by another company, or in the cloud remain working and functional.
A big misconception a lot of people have with the cloud is the it can't fail. They frequently do; in-fact their employees even openly state it. The benefit of the cloud is that you can move from those broken machines to working ones within minutes not hours. Who is going to move it for you at 3:00am? Also, who will know how to change the server's code so it works without issue on the new location and that no data was lost? This is why cloud providers charge a massive premium for their support and still won't help you with your software (code), only hardware.
No one wants to be replaced and while our team certainly can replace your entire on-site DevOps / IT team there is no need to. Our pricing is economical and our service is awesome as a supplement to your existing teams. We whole heartedly suggest you keep your on-site "web guy." It allows us to interface with someone that know exactly what is going on, and gives you someone to do the in-expensive mundane tasks. You in return no longer have to pay for overtime during indicents, gives you credibility as having a truly 24 hour team and you have someone who can pick up when your IT web guy can't make it. Kid's baseball game? We have you covered. Sick for the day? We'll fill in. Where are here to make everyone's lives easier.
We know that one of the biggest fears when a disaster happens is "What's going on? How do we solve this?" With NetZilla you never need to worry about this again. When something goes wrong your monitoring will notify our our sysadmins in the DevOps team and they start on your case. After they have assessed the situation you will be notified of what exactly the cause is, and how they are going to solve it. Not only that if you plan includes it they will be able to create a detailed report of how you can prevent this from happening in the future, and can even update your public status page / customers if you wish for them to.