-
Notifications
You must be signed in to change notification settings - Fork 43
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
Start using new eval history table #3703
Conversation
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.
A bit of semi-unrelated commentary on the metrics that I happened to notice.
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.
This cleanup is not directly related to the rest of the PR, right? (It's okay, just trying to make sure I understand.)
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.
I realized when I wired these metrics into the engine that I was using the wrong type for status.
eaf5228
to
6268bde
Compare
This PR wires the eval history service into the evaluation engine. It is gated behind a feature flag while we experiment with it. A follow on PR will add logging for remediation and alerting. Relates to #3556
7de1c11
to
cd843e8
Compare
cd843e8
to
b6d11cb
Compare
RuleEvalID: id, | ||
RuleEvalID: evalID, |
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.
I suppose it's intended but why did we switched from one to another?
This PR wires the eval history service into the evaluation engine. It is gated behind a feature flag while we experiment with it. A follow on PR will add logging for remediation and alerting.
Relates to #3556
Summary
Provide a brief overview of the changes and the issue being addressed.
Explain the rationale and any background necessary for understanding the changes.
List dependencies required by this change, if any.
Fixes #(related issue)
Change Type
Mark the type of change your PR introduces:
Testing
Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.
Review Checklist: