Alarm fatigue
Alarms that flap around a threshold and hundreds of notifications during maintenance hide what matters.
Alarm engine
Less noise. Earlier warnings.
The Netronus alarm engine evaluates the metrics of every module in the same rule editor. Durations and a separate recovery threshold cut needless alarms; forecast and baseline rules warn you before a problem grows. Before saving a rule you see how many times it would have fired in the last 24 hours.
The problem
What gets in the way today
Problems found too late
An alarm when the disk is already full is too late; the trend should be visible earlier.
A rule system per domain
Separate tools for network, servers and storage mean separate rules and separate notification settings.
The solution
One rule engine, every module
Rules are written against the metric dictionary and do not care about the data source: disk usage from SSH or from the agent triggers the same rule. Ready-made templates ship with the modules; thresholds can be overridden per folder, group or single asset.
- A condition per severity with a “for at least X minutes” duration
- A separate recovery threshold (hysteresis)
- No false “no data” alarms for assets that never sent data
Capabilities
What you get
Thresholds with hysteresis
Warning to critical levels, a “for at least X minutes” condition and a separate recovery threshold.
Rate of change
For example “usage grew by more than 10% in one hour”.
Forecast
Trend rules such as “this disk or pool will be full in 7 days”.
Seasonal baseline
Catches unusual deviation compared with the same hour in previous weeks.
No data / unreachable
Alarms when an asset stops sending data.
Maintenance windows
Alarms on assets in maintenance are visible but not notified; if still open when maintenance ends, they are notified.
Dependency suppression
While a host is down no separate alarms are raised for its VMs; suppression lifts when the parent recovers.
Flapping protection
An alarm that opens and closes often within a short time is flagged and its notifications stop.
E-mail, SMS and webhooks
Per-channel minimum severity, notify on recovery, repeat notifications and escalation; signed webhooks for ITSM, digest messages during alarm storms.
Rule preview
Try a rule on the last 24 hours before saving: how many times, at which severity, on how many series it would have fired.
Technical summary
At a glance
| Item | Detail |
|---|---|
| Rule types | Threshold, state, rate of change, forecast, dynamic baseline, no data |
| Severities | Information, Warning, Minor, Major, Critical |
| Scope | Asset type, folder, group, single asset, label filters and exclusions |
| Overrides | Asset > group > folder > rule precedence |
| Notification channels | E-mail, SMS, webhook (signed) |
| Suppression | Maintenance window, dependency, flapping, repeat |
| Scale test | 500,000 series, evaluated every minute |
| Large rules | Split automatically by series count |
See Netronus in your own environment
We will set up a demo on your network, show the screens with your own devices and prepare a quote for the modules you need.
Request a demoRelated
Better together
Platform and Scale
Network, servers, virtualization, storage, flow, logs, configuration and security in one interface. Only the modules you need; from one server to a cluster.
Explore the moduleServers and Agent
Monitor Linux and Windows servers agentless over SSH, WinRM, SNMP and Redfish, or in depth with the lightweight Netronus Agent.
Explore the moduleStorage
NetApp, Dell, Pure Storage, HPE, Huawei and IBM arrays plus Brocade and Cisco MDS SAN switches; see how many days are left before a pool fills up.
Explore the moduleSee Netronus in your own environment
We will set up a demo on your network, show the screens with your own devices and prepare a quote for the modules you need.