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

regendb: seed the alert_logs table #2150

Merged
merged 2 commits into from
Feb 15, 2022
Merged

regendb: seed the alert_logs table #2150

merged 2 commits into from
Feb 15, 2022

Conversation

dctalbot
Copy link
Contributor

@dctalbot dctalbot commented Feb 9, 2022

  • Identified the issue which this PR solves.
  • Read the CONTRIBUTING document.
  • Code builds clean without any errors or warnings.
  • Added appropriate tests for any new functionality.
  • All new and existing tests passed.
  • Added comments in the code, where necessary.
  • Ran make check to catch common errors. Fixed any that came up.

Description:
This PR adds records to alert_logs when running make regendb.

Which issue(s) this PR fixes:
Fixes #2138

How to test:

  1. Run make regendb
  2. Verify that alert_logs contains a "created" event for every alert, and that closed alerts have a corresponding "closed" event. Closed events are timestamped after the relevant created event.

@arurao arurao self-requested a review February 14, 2022 17:50
@dctalbot dctalbot merged commit 34e1ed1 into master Feb 15, 2022
@dctalbot dctalbot deleted the alert-logs-regendb branch February 15, 2022 16:03
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

Successfully merging this pull request may close these issues.

regendb: add alert_logs data
4 participants