Make Sure Those Red and Yellow Alerts Really Mean Something
The longer your network monitoring system dashboard is lit up in red and yellow without consequence, the less the alerts will mean to you. Netreo’s smart handling of application failure detection allows you to automatically test and re-test failed services to suppress false alarms easily and efficiently. Any given service can be retested any number of times before notifications are sent, and if the problem is caused by connectivity or host issues, the alerts can be suppressed automatically.
Schedule a DemoSmart Inventory
Before addressing alert thresholds, establish whether you even need to be monitoring a given device or system. A proper inventory of all of your organizational devices will help you make sure you’ve got visibility where you need it — and only where you need it.
As you prepare your network for a monitoring system installation, you can use either Netreo’s auto discovery process to inventory the systems and devices or simply manually inventory the devices yourself. Often times, an auto discovery process helps organizations identify key devices they hadn’t realized they could monitor so easily. Other times, a manual inventory can help you identify devices you probably don’t need to monitor.
From the Blog
One of our senior service engineers (SEs) was visiting a client not long after installing a network monitoring system. Looking the client’s dashboard, the SE saw something rare and wonderful. He said to the client, “Everything on your main page is green. Is that normal? Is everything (meaning the monitoring system) working okay?”
“Oh yeah. I run a pretty tight ship around here,” the client answered. “I know what’s supposed to be monitored and when. My thresholds are all dialed in. That way, if I go to Netreo’s UI and I see something yellow or red, I know for sure there’s a problem.”
Read the complete blog
Report Anomalies — Not Predictable Spikes
If your monitoring system is only looking for fixed threshold values, you might not be seeing the whole picture. Static thresholds, such as for server CPU or memory, can generate misleading alerts. A classic example is a SQL Database server. It might hit 100% CPU four times per day, but the organization doesn’t need to be alerted every time that happens. What’s really important is when the server is behaving unusually — Running at 80% at a specific time when it typically runs at 20%. This might indicate a problem with your application or users — but it won’t trigger a static alert. With Netreo’s anomaly detection, you will be alerted so you can find out what’s going on.
Have a Unique Alerting Situation?
Contact a member of our team today to discuss your situation.
Reach out!
Comprehensive, Consolidated Alerting
While enterprise-size organizations are unlikely to have zero alerts at any given time, zero alerts should be a goal that organizations of all sizes aspire to. Properly configured alerts are essential, and poorly configured alerts can be worse than having none at all.
Netreo’s comprehensive monitoring, alerting, and reporting helps prevent various tools in your organization from creating alert noise that most of your team doesn’t fully understand and can’t always respond to properly. Different tools’ alarm systems may use different protocols to poll their devices and likely have their own UI. Different UIs might force you to unnecessarily create silos within your network management operation.
Automatically Set Thresholds for New Network Devices
Because the work of monitoring your network is never done, Netreo helps you as you automate future growth. Our platform presets alert thresholds for specific device classes based on the parameters you’ve already set. While some new devices won’t require exactly the same alert parameters as the device class in general, preset thresholds will provide protection if the device’s alerts aren’t reconfigured immediately.