Cert monitoring using advance expiry results in an alert remaining in a Trouble state the entire duration (until the cert is replaced or expires). For example, a period set to ten days would keep the alert open for an extended period. This creates excessive noise in the alerts dashboard. Consequently it increases the chance that unrelated new alerts will be missed or actioned late.

Ideally the "Certificate expiry threshold" in the monitor's threshold profile (shown below) would include an "=" sign in the "Condition" field. Alerting would then come and go without being a persistent nuisance (perhaps by a user dismissing the alert or by the alert self-closing after staying open a defined, short period of time.)

Alternatively, the "Certificate expiry threshold" in the monitor's properties (shown below; same name as that which is used in the threshold profile; naming them differently would clarify functionality) would be limited to only sending a notification and not changing the monitor to a Trouble state. Alerting would then be controlled exclusively by the threshold profile.