ferruzzi commented on code in PR #53727: URL: https://github.com/apache/airflow/pull/53727#discussion_r2274045805
########## airflow-core/docs/howto/deadline-alerts.rst: ########## @@ -0,0 +1,312 @@ + .. Licensed to the Apache Software Foundation (ASF) under one + or more contributor license agreements. See the NOTICE file + distributed with this work for additional information + regarding copyright ownership. The ASF licenses this file + to you under the Apache License, Version 2.0 (the + "License"); you may not use this file except in compliance + with the License. You may obtain a copy of the License at + + .. http://www.apache.org/licenses/LICENSE-2.0 + + .. Unless required by applicable law or agreed to in writing, + software distributed under the License is distributed on an + "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + KIND, either express or implied. See the License for the + specific language governing permissions and limitations + under the License. + + +Deadline Alerts +=============== + +The :class:`~airflow.sdk.definitions.deadline.DeadlineAlert` feature is the next evolution of +the old SLA. Deadline Alerts allow you to set time thresholds for your DAG runs and automatically +respond when those thresholds are exceeded. You can set up Deadline Alerts by choosing a built-in +reference point, setting an interval, and defining a response using either Airflow's Notifiers or +a custom callback function. + +Creating a Deadline Alert +------------------------- + +Creating a Deadline Alert requires three mandatory and one optional parameter: + +* Reference: When to start counting from +* Interval: How far before or after the reference point to trigger the alert +* Callback: What to do when the deadline is exceeded +* Callback Kwargs: Optional values to pass to the Callback when it is run Review Comment: Good catch, it needs to be updated; there are now three mandatory and no optional after @ramitkataria 's recent PR merged. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
