ref(seer): Option to route severity to group-seer#115702
Merged
Merged
Conversation
github-actions
Bot
added
the
Scope: Backend
JoshFerge
approved these changes
May 18, 2026
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
2 participants
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.
wait for https://github.com/getsentry/ops/pull/20670
we're getting stockouts on L4s for the first time in a while. 1/5th of seer-gpu deploys hit them last week. GCP warned that L4s are legacy and to expect stockouts
i wanna move the very lightweight severity model to a lighter weight group-seer deployment while i transition group-ingest to a different machine type, and eventually transition group-seer to T4 GPUs or CPUs