feat(fortuna): add request_failovers_triggered metric
#3110
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
This metric tracks when backup replicas perform failover to fulfill requests that the primary replica failed to handle. It will be used for alerting when primary instances are not working correctly. Co-Authored-By: Tejas Badadare <tejas@dourolabs.xyz>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
aditya520
approved these changes
Oct 7, 2025
tejasbadadare
deleted the
devin/1759785133-add-request-failovers-triggered-metric
branch
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.
Summary
Add a counter than increments when a Fortuna replica acting as backup attempts to fulfill a request. This indicates that the primary replica failed to fulfill the request in time. We will add an alert based on increase of this metric to let us know the primary isn't working correctly.
How has this been tested?