Service Level Agreements (SLAs)
Service Level Agreements (SLAs)
Service Level Agreements (SLAs)
Service Level Agreements (SLAs) define expectations for data product delivery and freshness. Create SLAs to monitor whether your data products meet business requirements and configure alerts to notify your team when SLAs are at risk or violated. SLAs check for a successful run or update of the final assets in a data product.
Data products with tables as their final assets do not support SLAs.
Astro allows you to create Freshness, Timeliness and Custom SLAs on your data products. Based on the timeliness or freshness expectations defined in your SLAs, Astro uses SLA success rates to send proactive alerts and generate insights into your data pipelines.
Timeliness SLAs only support Standard Time. If you want Local Time support, you must adjust the SLA’s UTC time when the time changes from Standard Time to Daylight Savings Time or from Daylight Savings Time to Standard Time. All evaluation times are in UTC, consistent with Airflow.
0 0 1-10 1,4,7,10 *The minimum interval is 15 minutes to prevent excessive evaluation frequency.
The maximum freshness window is 31 days.
Evaluation schedules longer than 1 day evaluate on the nth day of the month and begin on the first of the month. For example, an evaluation schedule of 9 days set on December 31 will evaluate on Jan 1st, Jan 10th, Jan 19th, Jan 28th, Feb 1st, Feb 10th, Feb 19th, Feb 28th, March 1st, etc.
After you create an SLA, you can configure alerts and proactive alerts.
After you create an SLA, Astro keeps a record of the rate at which your data product hits or misses the SLA. You must configure an Alert or a Proactive Alert to receive notifications when your pipeline experiences an SLA miss or when an upstream process might cause an SLA miss or a failure.