This is an automated email from the ASF dual-hosted git repository.

potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git


The following commit(s) were added to refs/heads/main by this push:
     new 6199f1ffc8 Update metrics.rst for param dagrun.schedule_delay (#36404)
6199f1ffc8 is described below

commit 6199f1ffc807c55cbcc36f834e06b9791ce222ca
Author: Bowrna <[email protected]>
AuthorDate: Sun Dec 24 22:01:09 2023 +0530

    Update metrics.rst for param dagrun.schedule_delay (#36404)
    
    The timer in statsd client if passed the timedelta, converts into 
milliseconds rather than seconds.
---
 .../administration-and-deployment/logging-monitoring/metrics.rst        | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/docs/apache-airflow/administration-and-deployment/logging-monitoring/metrics.rst
 
b/docs/apache-airflow/administration-and-deployment/logging-monitoring/metrics.rst
index 54efc7501e..a973f4e69e 100644
--- 
a/docs/apache-airflow/administration-and-deployment/logging-monitoring/metrics.rst
+++ 
b/docs/apache-airflow/administration-and-deployment/logging-monitoring/metrics.rst
@@ -233,7 +233,7 @@ Name                                                        
     Description
 ``dag_processing.last_duration.<dag_file>``                      Seconds taken 
to load the given DAG file
 ``dagrun.duration.success.<dag_id>``                             Seconds taken 
for a DagRun to reach success state
 ``dagrun.duration.failed.<dag_id>``                              Seconds taken 
for a DagRun to reach failed state
-``dagrun.schedule_delay.<dag_id>``                               Seconds of 
delay between the scheduled DagRun
+``dagrun.schedule_delay.<dag_id>``                               Milliseconds 
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

Reply via email to