NetCrunch Platform Module

Advanced Monitoring
and Alerting

Set status for redundant connections with Business Status Node and avoid false positives with advanced thresholds and alerting conditions.

This module is included in

it can be added to any NetCrunch platform product.

@Performance Chart

Download NetCrunch Trial

Setting an upper or lower threshold seems to be simple, right? What happens when the value is oscillating and goes over and under the threshold boundary every minute? Unfortunately, you get an alert every other minute.

This situation is just an example of why some simple models fall short sometimes, and you need to reach for a bit more advanced features like thresholds with separate reset boundaries.

Another example might be when you want to react only if both connections fail. Otherwise, you need just a notification. Advanced monitoring algorithms are the answer to these specific needs that might be not frequent but sometimes indispensable.


    1. Use advanced alerting conditions to trigger alerts even when the event did not happen (like missing backup or heartbeat).
    2. Use Business Status Node to represent and calculate the status from multiple monitored elements.
    3. Use advanced thresholds to detect abnormal behavior and avoid false positives.
  • Advanced Alerting

    NetCrunch expands beyond traditional network device monitoring. Practically it can monitor any process and devices where a reaction time might be 15 seconds more.

    @Alerting Conditions

    Conditional Alerts

    NetCrunch can process events from many external sources that can behave unusually. That's why we have equipped NetCrunch in a range of additional conditions that you can add to any alert. NetCrunch provides conditional alerting, which allows monitoring heartbeats or react to missing events. It also can make the alert less sensitive to repetitive events.


    All NetCrunch internal alerts are correlated. For other external alerts (i.e., traps, syslog messages), it allows adding a list of actions to the alert that can close the alert. The alert can also be closed automatically after a given time. This kind of event has to occur on the same node.

    Another correlation can be defined for alerts happening on different nodes within the same time frame.

    Read more at Alert Conditions & Correlation

  • Business Status Node

    A node in NetCrunch is an Atlas entity, a group of services usually representing a network endpoint (interface)

    @Business Status Node

    Nevertheless, NetCrunch node can represent much more than just a network endpoint now, as the network monitoring model has evolved from simply looking at devices, later as a set of endpoints. Finally, we see a cloud of services.

    The node often doesn't need an IP address now. Such a node is a Business Status node representing a state of a group of services (nodes, sensors service, or monitoring packs) that is calculated automatically.

    You can add multiple elements to each group that translate to a logical condition determining the node's state.

    Business status can rely on another status node to easily create a path of critical services by building a chain of Business Status nodes.

  • Advanced Thresholds

    @Falling Threshold

    Unlike entry-level monitoring products, NetCrunch offers a vast range of threshold conditions, including baselines for professional usage.

    These thresholds will help you avoid false-positive alerts and detect abnormal behavior or an abrupt change of the monitored value,

    Event Triggers for Counters


NetCrunch is built upon solid statistical analysis. The program offers high accuracy with somewhat lower precision to achieve a high level of performance.

Raw Data

NetCrunch stores both raw data and pre-computed data samples. Depending on the analysis level, the program uses different data streams to present data on the screen (you need no more data than your screen can display) accurately.