Don't trigger unexpected event alerts for empty usage hashes in redis#11331
Merged
Don't trigger unexpected event alerts for empty usage hashes in redis#11331
Conversation
vadimberezniker
approved these changes
Feb 17, 2026
bduffany
force-pushed
the
unexpected-empty-hash
branch
from
0050050 to
3b8cf7f
Compare
bduffany
force-pushed
the
unexpected-empty-hash
branch
from
3b8cf7f to
efdc0b9
Compare
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.
These are more or less expected when redis restarts, and we already have alerts for redis restarts anyway. Replacing these UnexpectedEvents with a metric so that we can track frequency instead and alert if we see too many of them.