Alerting at scale #7
Merged
Conversation
This file contains 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
|
@wpjunior, I have a suggestion: if you could write a some inline docs and comments, it would help those reading the code. |
wpjunior
force-pushed
the
alerting-at-scale
branch
from
4bf2063
to
8aeb872
Compare
vierno
reviewed
Dec 18, 2019
|
Thanks, @vierno for your given review. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Based on lessons of https://landing.google.com/sre/workbook/chapters/alerting-on-slos/#alerting_at_scale
The initial motivation is to standardize a set of SLOs and help teams to classify many microservices without pain.
Could you review? @vierno, @pedrokiefer, @MayconDionisio