You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by ep...@apache.org on 2022/11/09 14:35:24 UTC
[airflow] 19/29: Correct timer units to seconds from milliseconds. (#27360)
This is an automated email from the ASF dual-hosted git repository.
ephraimanierobi pushed a commit to branch v2-4-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
commit f1073dbcdb99e44e3386ae33bc68e394414e8a1d
Author: Jacob <ja...@gmail.com>
AuthorDate: Mon Nov 7 16:25:17 2022 -0600
Correct timer units to seconds from milliseconds. (#27360)
``dagrun.duration.success.<dag_id>``
``dagrun.schedule_delay.<dag_id>``
``dagrun.<dag_id>.first_task_scheduling_delay`` are reported to statsd in seconds, not milliseconds. Other timers in this list might be suspect, but I haven't checked them yet.
(cherry picked from commit 25d7ca918e2d382cccd7d70386a1055d33bb517b)
---
docs/apache-airflow/logging-monitoring/metrics.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/apache-airflow/logging-monitoring/metrics.rst b/docs/apache-airflow/logging-monitoring/metrics.rst
index d92327905f..a5baa902d0 100644
--- a/docs/apache-airflow/logging-monitoring/metrics.rst
+++ b/docs/apache-airflow/logging-monitoring/metrics.rst
@@ -155,12 +155,12 @@ Name Description
``dagrun.dependency-check.<dag_id>`` Milliseconds taken to check DAG dependencies
``dag.<dag_id>.<task_id>.duration`` Milliseconds taken to finish a task
``dag_processing.last_duration.<dag_file>`` Milliseconds taken to load the given DAG file
-``dagrun.duration.success.<dag_id>`` Milliseconds taken for a DagRun to reach success state
+``dagrun.duration.success.<dag_id>`` Seconds taken for a DagRun to reach success state
``dagrun.duration.failed.<dag_id>`` Milliseconds taken for a DagRun to reach failed state
-``dagrun.schedule_delay.<dag_id>`` Milliseconds of delay between the scheduled DagRun
+``dagrun.schedule_delay.<dag_id>`` Seconds of delay between the scheduled DagRun
start date and the actual DagRun start date
``scheduler.critical_section_duration`` Milliseconds spent in the critical section of scheduler loop --
only a single scheduler can enter this loop at a time
-``dagrun.<dag_id>.first_task_scheduling_delay`` Milliseconds elapsed between first task start_date and dagrun expected start
+``dagrun.<dag_id>.first_task_scheduling_delay`` Seconds elapsed between first task start_date and dagrun expected start
``collect_db_dags`` Milliseconds taken for fetching all Serialized Dags from DB
=================================================== ========================================================================