Upgrading synthetic metric rules
Synthetic metric rules in the current version are defined differently from earlier versions, enabling more choices and capabilities in rule definitions.The upgrade process migrates the same functionality from earlier versions into the current rule definitions.
To conform to the new rule definitions, the upgrade process adapts the following specific rules:
|Metric rule||Rule definition in earlier version||Rule definition in current version|
|Out-of-the-box metric rules|
|Custom metric rules|
In earlier versions, the metric rule defines the number of consecutive breaches that a minor or critical threshold is breached before opening an event. That is, the Consecutive value is the number of consecutive executions (one after the other) that violate the threshold before opening an event.
In the following image, an event opens with a minor status if the transaction is longer than five seconds, eight times in a row, or with a Critical status if the transaction is more than nine seconds long, eleven times in a row.
Part of synthetic metric rule definition for early versions (10.7–11.0.x)
In the current version, the metric rule defines the violation frequency—that is, if the event conditions are breached x out of y times.
After the upgrade process, if the rule in the previous image is the predefined performance rule, both thresholds are retained but the violation frequency is set to 11 out of 11 execution cycles.
Part of the synthetic metric rule definition for the current version
If the rule is for a custom timer, then two separate rules are created:
- A rule with the minor threshold and the violation frequency set to 8 out of 8 execution cycles
- A rule with the critical threshold and the violation frequency set to 11 out of 11 execution cycles