What Changed From the Previous Monitoring

Previously, every environment had its own copy of the monitoring conditions. Now one alert rule covers all environments by default. Where your environments had different settings, the migrated rules are limited to the environments they came from.

Single-metric conditions such as "aggregate lock time", "aggregate load time" and "aggregate error rate" are now conditions of one rule, Bad performing aggregate, each with its own severity. A rule fires when any of its conditions holds, and an alert escalates as more severe conditions start holding.

Thresholds you had changed were carried over unchanged. A customized condition that did not fit a new default rule became a rule of its own, named after the old condition and starting with Legacy, for example Legacy processor ingest latency (> 100). You can rename, merge, or delete these rules.

The new default rules use different thresholds for some metrics, most visibly the handler error rate, Axon Server disk space and the connection limits. This only affects thresholds you had not customized.

A condition you had set up for one specific handler, processor, or other subject is now an exception on the matching condition of the rule. If there was no matching condition, it became a separate rule filtered to that subject.

Instead of one alert per subject, the alerts of a rule in one environment are collected in one inbox item, with one notification per item. To get separate items again, for example per application, set Split inbox by on the rule.

You can snooze and archive inbox items, and alerts can wait a while before resolving (Resolve after) so a flapping subject does not notify you over and over.

Alerts that were active or resolved before the switch are not in the new inbox.