LogicMonitor recognized as a Customers' Choice by Gartner Peer Insights™ in 2024 Gartner Voice of the Customer for Observability platforms.

Read More

Cluster Alerts

Last updated on 13 February, 2025

Cluster alerts monitor and alert on datapoints across multiple resources in a resource group. They are designed to provide quick insight into the overall state of a collection of devices or cloud resources. For example, this can be useful when you have a pool of resources that are serving an application or performing a task; while you may not be too concerned with an issue that affects a single resource in the pool, you’ll likely want to know immediately if the pool of resources as a whole is at risk of not being able to serve its purpose. In a case like this, you could configure a cluster alert to trigger when five batch servers have CPU usage rates higher than 80%.

Cluster alerts trigger based on the presence of individual alerts for devices or instances belonging to the same group of resources. For example, using the scenario provided in the previous paragraph, five batch servers in the group would need to have 80% set as an alert threshold for CPU usage and would need to have exceeded that threshold in order for the cluster alert to trigger. Because cluster alerts rely on individual datapoint alerts, it’s important that you keep datapoint thresholds tuned. For more information, see Tuning Static Thresholds for Datapoints.

Note: Cluster alerts are a simple way to measure the overall health of a group of resources. For more sophisticated monitoring and alerting capabilities across groups of resources, consider LM Service Insight, a feature that groups instances across one or more monitored resources (For example, devices) into logical “Services”. For more information, see About LM Service Insight.

Requirements for Adding Cluster Alerts

You need to have access to a resource group with existing resources.

Adding Cluster Alerts

  1. In LogicMonitor, navigate to Resources Tree, and select the resource group for adding the cluster alert.
  2. From the Resource group’s detail view, select the Cluster Alerts Tuning tab.
  3. Select the Add Cluster Alert icon add cluster alert in the upper right corner to open the Add Cluster Alert dialog.
    ClusterAlert-Add
  4. In the When dropdown menu, select the comparison operator to configure the condition for cluster alert. The available options are as follows: equal to, more than, less than, more than or equal to, less than or equal to.
  5. Enter a numeric value to choose percentage or total number for the instances or resources.

Note: You can enter 3 threshold values separated by a space. The first value corresponds to warning, the second to error, and the third value corresponds to critical. 

  1. Select total to indicate that the threshold is a static device or instance count. Select % of (percentage of) to indicate that the threshold is a percentage of the total number of resources or instances in the group.
  2. Select resources or instances to indicate whether the threshold count or percentage is calculated using the number of resources in alert or the number of instances.
  3. In the have a minimum of alert severity of dropdown menu, select CriticalError, or Warning.
  4. Select values for the DataSource and Datapoints from the dropdown menu to check if they meet the minimum alert severity level specified above.
  5. Toggle the Trigger a cluster alter on or off to start or stop sending the cluster alert.
  6. Toggle the Suppress the individual alerts (Recommended) on or off to suppress single alerts.

Note: It is recommended to suppress the individual alters and use the cluster alerts instead. The individual alerts that are suppressed still appear in the alerts table but notifications are not routed for these alerts.

  1. Select Save.

In This Article