As part of Extension 2.0, alert (metric events) definitions can be defined. Unfortunately each version update causes replace of these definitions and reset of their configs (removal of custom properties, disabling of enabled alerts, etc).
This issue can be solved by copying default alerts to separate custom instances, but introduces different issue, that copied custom alert can use old metric labels/structure that doesn't fit with updated extension version (and is covered with new version of alert definitions).
So after each extension version update it's neccesary to perform one of these steps (depending on selected alert strategy above):
- define customizations in new alerts
- compare new alerts with copied custom ones to find possible issues with metric name/structure definitions
Not sure which of these strategies is better nor recommended one. Can anyone share recommendations with Extensions 2.0 Alerts lifecycle?
Alanata a.s.
