New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DM-35878: escalate alarms to OpsGenie #52
Conversation
089eb42
to
588c1bd
Compare
a5b6df0
to
5f911bc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general this looks great. I particularly like the mock OpsGenie. I did find a few typos and other things I commented on. I leave it to you to process or ignore them.
f"{escalation_delay=} must be > 0 if and only if" | ||
f"{escalation_responders=} is not empty" | ||
) | ||
self.escalation_responders = list(escalation_responders) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is an explicit cast to list
needed here if the doc string for escalation_responders
already indicates that it is a list?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't try for fully correct types in doc strings (only in formal Python type annotations). list is the shortcut I always for any generic ordered sequence.
5f911bc
to
0ba0117
Compare
Update the config schema and Alarm to support new fields for responders. Update the model to set those fields. Update the CSC to create a new OpsGenie alert when an alarm's do_escalate field is set.
* Split into User Guide and Developer Guide * Add a section on escalation
0ba0117
to
2b9313e
Compare
No description provided.