changes made#604
Merged
Merged
Conversation
Added comprehensive SLO documentation in [docs/SLO.md](cci:7://file:///c:/Users/SWAYY/3D%20Objects/Credence-Backend/docs/SLO.md:0:0-0:0) defining 99.9% success rate and 250ms latency targets with error budget calculations and burn rate alerting thresholds. Updated Prometheus alert configuration to use proper burn rate calculation `(current_error_rate / 0.001) > 2` instead of hardcoded multiplier. Added 19 tests validating Prometheus alerts configuration including burn rate threshold, SLO violation alerts, and overall alert structure.
|
@Swayymalcolm99 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
5 tasks
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
3 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.
Closed #571
Added comprehensive SLO documentation in docs/SLO.md defining 99.9% success rate and 250ms latency targets with error budget calculations and burn rate alerting thresholds. Updated Prometheus alert configuration to use proper burn rate calculation
(current_error_rate / 0.001) > 2instead of hardcoded multiplier. Added 19 tests validating Prometheus alerts configuration including burn rate threshold, SLO violation alerts, and overall alert structure.