-
Notifications
You must be signed in to change notification settings - Fork 253
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
admin: add alert auto-close feature #2660
admin: add alert auto-close feature #2660
Conversation
# Please enter a commit message to explain why this merge is necessary, # especially if it merges an updated upstream into a topic branch. # # Lines starting with '#' will be ignored, and an empty message aborts # the commit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We settled on a design for this: #2658 (comment)
@Lakshmi2107 let us know if you'd like any help implementing the changes, thanks for the PR! |
thank you @mastercactapus. We are good for now. We will update the implementation once done. @Lakshmi2107 |
@mastercactapus Updated PR with auto-close changes. Please review. |
@mastercactapus Thanks for the comments. I have pushed all suggested changes. Please review. |
…2107/goalert into feature/auto-close-alert # Conflicts: # engine/cleanupmanager/db.go
@mastercactapus Addressed all review comments. Please check |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!!!
I pushed a couple of tweaks to wrap this up:
- re-ordered things to be AlertCleanup, then AlertAutoClose, everywhere
- Added a small smoke test to validate the functionality
- added a
coalesce
to the EP notice query, as it caused a NULL error when there were no escalation policy steps
Thanks @mastercactapus |
thank you so much @mastercactapus @Lakshmi2107 |
Description:
GoAlert sends alerts to various communication methods, once the alert is created it will be in unacknowledged state. there are some alerts that are in unack state forever. Any alert created in the goalert especially for monitoring production systems should have some lifecycle and close beyond some time say 24 hrs, otherwise it won't be meaningful.
Which issue(s) this PR fixes:
Fixes #2658
Screenshots:

Additional Info:
Need to add a few rows in config_limits table and add values to the config limit enum
alter type enum_limit_type add value 'maximum_time_to_auto_close_alert';
Rows to be inserted in table config_limits
Max time to auto-close an alert ( in hours )
Example:
"maximum_time_to_auto_close_alert" 3