engine: new module for alert metrics#2177
Merged
Merged
Conversation
mastercactapus
previously approved these changes
Mar 7, 2022
mastercactapus
previously approved these changes
Mar 7, 2022
mastercactapus
approved these changes
Mar 8, 2022
KatieMSB
approved these changes
Mar 8, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
make checkto catch common errors. Fixed any that came up.Description:
This PR introduces a new engine module for creating and populating a new
alert_metricstable. It prioritizes newly-closed alerts, but will eventually process all remaining closed alerts.Which issue(s) this PR fixes:
Fixes #2121
How to review:
make regendbengine/metricsmanager/update.gomake startengine_processing_versions.statecolumn is populatedalert_metricstable is populatedAdditional Info:
idcolumn in order to be compatible with the switchover tool.