What good is an alert that file system X is at 80% without any context. Okay so the file system is at 80% but is this an anomaly or is it a trend? A trend should never set off an alert. System resources should be tracked and trends addressed before they become problems. This is what we call proactive enterprise monitoring.
Don't feel like doing the math? Find your industry in the downtime table.
Monitoring is supposed to allow your technical staff to focus on the future needs of the business rather than fighting fire after fire. Far too often monitoring is implemented as a ping and page service, your staff learns of an issue right after your users do. While this can not be prevented in all situations it should not be the norm. Proactive monitoring gives your staff the tools they need to be aware of the status of your computing environment to prevent or predict that next call to the help desk.
Proactive monitoring can lower your costs through increased productivity, capacity planning, and reduced unplanned downtime. Many technology staff members spend significant parts of their day reacting to issues in the environment. Most issues are easier to prevent than to repair, when potential problems are resolved before they happen it helps refocus your staff, instead of looking at today needs they will be planning for tomorrows.
With every new server comes increased expense from data center space to electricity to staff. Being able to determine if you have the right resources in the right place is mandatory. By analyzing the utilization of your equipment you can better determine its capacity and decide to add or consolidate.
Unplanned downtime may be more expensive than you thought. There are many hidden costs. From productivity and revenue to employee morale and customer opinion. Use this formula to calculate a rough estimate for your business.
Estimated cost per hour =
(Employee/hr x Percent of affected Employees) + (Average Income per hour x Percent of affected income)
Please keep in mind that this formula does not take into account the loss of goodwill and many other soft costs.
Formula source: "A Simple Way to Estimate the Cost of Downtime" David A. Patterson Computer Science Division, University of California at Berkeley