Alert Threshold Overview
Last updated on 17 January, 2025Receiving many meaningless LogicMonitor alert notifications can ultimately lead to you as a person ignoring important alerts. Conversely, not receiving a key alert could result in service downtime or even an outage. One of the keys to avoiding both of these undesirable situations is to add datapoint alert thresholds for your unique environment.
Datapoints, as defined by DataSources, are not the only originators of alerts (For example, alerts can be raised by monitored websites, EventSources, and so on as discussed in What does LogicMonitor alert on?), but they are the most common alert triggers and, therefore, making necessary adjustments can go a long way toward reducing unwanted alert noise.
There are two types of alert thresholds:
- Static Threshold—It consists of a timeframe; comparison method and operator; and up to three threshold values for triggering different alert severity levels. For more information, see Static Thresholds for Datapoints.
- Dynamic Threshold—They are calculated by algorithms and automatically trigger alerts when datapoint values are deemed anomalous. For more information, see Dynamic Thresholds for Datapoints.
You can add both static and dynamic thresholds to a single datapoint. For more information, see Assigning Both Static and Dynamic Thresholds to a Datapoint.
Other datapoint settings (in addition to static and dynamic thresholds) that can impact alert noise include the following:
- Alert trigger intervals—Consists of how many consecutive polling cycles a threshold must be exceeded for an alert to trigger).
- Alert clear intervals—Consists of how many consecutive polling cycles datapoint values must remain below the threshold before an alert clears).
- No Data alert behavior—Consists of triggering an alert due to absence of expected data.
For more information on how settings are configured from the global DataSource definition, see Datapoint Overview.