Repository navigation
Post: page, ticket or ignore, is the cheap model good enough for alert triage - #1935
Merged
Merged
Conversation
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
1 participant
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.
Eight configurations on DigitalOcean Serverless Inference (six open-weight models, two Inference Router routes) route 200 generated alerts against one written on-call policy, three runs each. Covers accuracy, missed pages, cost, latency, what the routers picked, and a test-data bug the models caught.
Repo: https://github.com/The-DevOps-Daily/alert-triage-bench
https://claude.ai/code/session_01FRYkaYp9vFJjWBjAQdjnQ4