You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current behavior for log monitors:
• Missing data group alerts auto-resolve (via expiry) after 7 days.
• Critical and warning ones also auto-resolve after 7 days of missing data.
Current behavior for metrics monitors:
• Missing data alerts auto-resolve (via expiry) after 1 day.
• Critical and warning ones auto-resolve after "query time range" + some delta. So if query time range is 15 mins, it can be anywhere between 15 to 20 mins depending on the scenario.
My recommendation:
• Logs missing data alerts should auto-resolve after 1 day (via expiry) - same as metrics ones: needs code changes.
• Logs critical and warning continue to remain in triggered state as long as alert condition continues to match.
• We should document the current behavior. cc <@UK8GRBSQZ> to verify logs one and <@UMYT715GR> for metrics one. Since this is a little complex, please provide the exact content.
Current behavior for log monitors:
• Missing data group alerts auto-resolve (via expiry) after 7 days.
• Critical and warning ones also auto-resolve after 7 days of missing data.
Current behavior for metrics monitors:
• Missing data alerts auto-resolve (via expiry) after 1 day.
• Critical and warning ones auto-resolve after "query time range" + some delta. So if query time range is 15 mins, it can be anywhere between 15 to 20 mins depending on the scenario.
My recommendation:
• Logs missing data alerts should auto-resolve after 1 day (via expiry) - same as metrics ones: needs code changes.
• Logs critical and warning continue to remain in triggered state as long as alert condition continues to match.
• We should document the current behavior. cc <@UK8GRBSQZ> to verify logs one and <@UMYT715GR> for metrics one. Since this is a little complex, please provide the exact content.
Slack Message
The text was updated successfully, but these errors were encountered: