KulykDmytro opened a new issue #22532: URL: https://github.com/apache/airflow/issues/22532
### Apache Airflow version 2.2.4 (latest released) ### What happened When inspecting metadata in airflow tables about sla stuff found that * in case of daily DAG's schedule `execution_date` attribute for `sla_miss` is filled with unexpected value. Seems like `data_interval_end` <img width="853" alt="image" src="https://user-images.githubusercontent.com/34435869/160167261-61212415-e662-4972-8e70-b69e8c3ada4b.png"> * in case of hourly schedule `sla_miss.execution_date` are as expected (equals to DAGRun's `data_interval_start`/`logical_date`/`execution_date`) this prevents to create any custom SLA analisys dashboards/metrics because unable to join `sla_miss` and `dag_run`/`task_instance` in direct and clear way clicking on daily task's link on SLA Miss dashboard forwarding to task instance which was never executed (because it is in "future") and have no runtime metrics in `Task instance details` All screenshots are taken @ 2022-03-25 17:xx:xx Z <img width="1789" alt="image" src="https://user-images.githubusercontent.com/34435869/160169174-11a89059-2fcb-4a1c-a837-25fdd64461c5.png"> ### What you think should happen instead `sla_miss.execution_date` should be same as `dag_run.execution_date` in all cases ### How to reproduce setup a dag with any daily schedule setup an SLA on task wait `sla miss` to trigger observe in `SLA Miss` dashboard - incorrect ### Operating System amazon linux ### Versions of Apache Airflow Providers _No response_ ### Deployment Official Apache Airflow Helm Chart ### Deployment details _No response_ ### Anything else _No response_ ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- 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]
