Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Log Monitors behavior fix #1211

Open
kimsauce opened this issue Dec 21, 2022 — with Slack · 0 comments
Open

Log Monitors behavior fix #1211

kimsauce opened this issue Dec 21, 2022 — with Slack · 0 comments
Assignees

Comments

Copy link
Collaborator

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

@kimsauce kimsauce changed the title Update Monitors doc Log Monitors behavior fix Jan 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants