-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Deployment SLA Definitions #16574
Deployment SLA Definitions #16574
Conversation
CodSpeed Performance ReportMerging #16574 will not alter performanceComparing Summary
|
we use
|
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.
Awesome tests! I have a few small comments, but overall this is looking great!
Co-authored-by: Alex Streed <[email protected]>
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.
LGTM!
This PR adds a new interface to deployments: SLAs. Service Level Agreements (SLAs) describe the intended behavior of the deployment. The first SLA we introduce here is the
TimeToCompletionSla
, which indicates how long flow runs from the deployment should take. It's possible to configuren
SLAs for a given deployment byflow.deploy
,prefect deploy ---sla
orprefect.yaml
. SLAs have different severities, giving users different alerting options for less or more serious violations.Checklist
<link to issue>
"mint.json
.