Alert Evaluation Logic: If CPU_sys for any node within a service is greater than 60, then an alert notification will be generated for that service (if it was not already generated).Metrics Monitor with Single Alert Group Ī user wants to create a monitor to track CPU across services, and wants to get notified if any node within a service has CPU > 60%. Notifications will not be sent for alert groups that already have an active alert. The input field has an auto-completion dropdown that allows you to select all the applicable fields from your query. In the example below, you would receive one alert for each service that has error count greater than 50. You can pick more than one field for the grouping condition.

One alert per : Allows you to receive one notification per each unique value of the grouping field(s).One alert per monitor: Choose this option if you want to only receive a single alert for the entire monitor.Enter your logs query, then select your desired Alert Grouping option:.Configure the rest of your Alert Condition per standard procedure.In the example below, user will receive one notification when CPU utilization is higher than the threshold for each unique AWS namespace within an account. One alert per : allows you to receive one notification per each unique value of the grouping field(s).One alert per time series: To receive a single alert for each time-series that is present in the metric query.One alert per monitor: If you only want to receive a single alert for the entire monitor.Enter your metrics query, then select your desired Alert Grouping option.Go to Manage Data > Monitoring > Monitors.Setup Īlert Grouping works for both Logs and Metrics Monitors. Rather than creating multiple monitors for each service, you can create one single monitor that does this. For this example below, let's say you're monitoring the ErrorRate for all of your services and want to get an alert for each service that breaches a specific error threshold. You can also have a monitor generate and resolve more than one alert based on specific conditions. You could group by _collector field, for example, and one alert would be generated per _collector. Each unique value of the field(s) will be evaluated against the alerting and resolution conditions, and if it meets the threshold, an alert will be fired and resolved respectively. Because even in times of globalization and increasing anonymity of services, MULTIMON continues to stand for proximity - proximity to our customers and business partners.Alert Grouping gives you the flexibility to customize how your alerts and notifications are generated from monitors, allowing you to specify a grouping condition based on a specific field(s). Our repair and maintenance service also guarantees the permanent operational readiness of the fire protection systems after installation. We have already assisted around 1,600 well-known customers (B2B) from industry, trade, logistics and the service sector in the construction of fire alarm systems and have always convinced them with our wide-ranging fire protection expertise. Our highly qualified teams of experts are on hand to provide analysis and advice in each of these phases of the project and, together with experienced engineers, technicians and fitters, design and implement the customized extinguishing system. The project planning of our automatic fire protection systems is mainly done on a turnkey basis, which means that we deliver everything from planning to installation and commissioning from a single source.

In multimon groups are empty error