Metrics Configuration

Airflow can be set up to send metrics to StatsD or OpenTelemetry.

Setup - StatsD

To use StatsD you must first install the required packages:

pip install 'apache-airflow[statsd]'

then add the following lines to your configuration file e.g. airflow.cfg

[metrics]
statsd_on = True
statsd_host = localhost
statsd_port = 8125
statsd_prefix = airflow

If you want to use a custom StatsD client instead of the default one provided by Airflow, the following key must be added to the configuration file alongside the module path of your custom StatsD client. This module must be available on your PYTHONPATH.

[metrics]
statsd_custom_client_path = x.y.customclient

See Modules Management for details on how Python and Airflow manage modules.

Setup - OpenTelemetry

To use OpenTelemetry you must first install the required packages:

pip install 'apache-airflow[otel]'

An OpenTelemetry Collector (or compatible service) is required for connectivity to a metrics backend. Add the Collector details to your configuration file e.g. airflow.cfg

[metrics]
otel_on = True
otel_host = localhost
otel_port = 8889
otel_prefix = airflow
otel_interval_milliseconds = 30000  # The interval between exports, defaults to 60000
otel_service = Airflow
otel_ssl_active = False

Note

To support the OpenTelemetry exporter standard, the metrics configurations are transparently overridden by use of standard OpenTelemetry SDK environment variables.

OTEL_EXPORTER_OTLP_ENDPOINT and OTEL_EXPORTER_OTLP_METRICS_ENDPOINT supersede otel_host, otel_port and otel_ssl_active
OTEL_METRIC_EXPORT_INTERVAL supersedes otel_interval_milliseconds

See the OpenTelemetry exporter protocol specification and SDK environment variable documentation for more information.

Enable Https

To establish an HTTPS connection to the OpenTelemetry collector You need to configure the SSL certificate and key within the OpenTelemetry collector’s config.yml file.

receivers:
  otlp:
    protocols:
      http:
        endpoint: 0.0.0.0:4318
        tls:
          cert_file: "/path/to/cert/cert.crt"
          key_file: "/path/to/key/key.pem"

Allow/Block Lists

If you want to avoid sending all the available metrics, you can configure an allow list or block list of prefixes to send or block only the metrics that start with the elements of the list:

[metrics]
metrics_allow_list = scheduler,executor,dagrun,pool,triggerer,celery

[metrics]
metrics_block_list = scheduler,executor,dagrun,pool,triggerer,celery

Rename Metrics

If you want to redirect metrics to a different name, you can configure the stat_name_handler option in [metrics] section. It should point to a function that validates the stat name, applies changes to the stat name if necessary, and returns the transformed stat name. The function may look as follows:

def my_custom_stat_name_handler(stat_name: str) -> str:
    return stat_name.lower()[:32]

Other Configuration Options

Note

For a detailed listing of configuration options regarding metrics, see the configuration reference documentation - [metrics].

Metric Descriptions

Counters

Name	Legacy Name	Description
`{job_name}_start`	`-`	Number of started `{job_name}` job, ex. `SchedulerJob`, `LocalTaskJob`
`{job_name}_end`	`-`	Number of ended `{job_name}` job, ex. `SchedulerJob`, `LocalTaskJob`
`{job_name}_heartbeat_failure`	`-`	Number of failed Heartbeats for a `{job_name}` job, ex. `SchedulerJob`, `LocalTaskJob`
`local_task_job.task_exit`	`local_task_job.task_exit.{job_id}.{dag_id}.{task_id}.{return_code}`	Number of `LocalTaskJob` terminations with a `{return_code}` while running a task `{task_id}` of a Dag `{dag_id}`. Metric with job_id, dag_id, task_id and return_code tagging.
`operator_failures`	`operator_failures_{operator_name}`	Operator `{operator_name}` failures.
`operator_successes`	`operator_successes_{operator_name}`	Operator `{operator_name}` successes.
`ti_failures`	`-`	Overall task instances failures. Metric with dag_id and task_id tagging.
`ti_successes`	`-`	Overall task instances successes. Metric with dag_id and task_id tagging.
`previously_succeeded`	`-`	Number of previously succeeded task instances. Metric with dag_id and task_id tagging.
`task_instances_without_heartbeats_killed`	`-`	Task instances without heartbeats killed. Metric with dag_id and task_id tagging.
`scheduler_heartbeat`	`-`	Scheduler heartbeats
`dag_processor_heartbeat`	`-`	Standalone Dag processor heartbeats
`dag_processing.processes`	`-`	Relative number of currently running Dag parsing processes (ie this delta is negative when, since the last metric was sent, processes have completed). Metric with file_path and action tagging.
`dag_processing.processor_timeouts`	`-`	Number of file processors that have been killed due to taking too long. Metric with file_path tagging.
`dag_processing.other_callback_count`	`-`	Number of non-SLA callbacks received
`dag_processing.file_path_queue_update_count`	`-`	Number of times we’ve scanned the filesystem and queued all existing Dags
`dag_file_processor_timeouts`	`-`	(DEPRECATED) same behavior as `dag_processing.processor_timeouts`
`dag_processing.manager_stalls`	`-`	Number of stalled `DagFileProcessorManager`
`dag_file_refresh_error`	`-`	Number of failures loading any Dag files
`scheduler.tasks.killed_externally`	`-`	Number of tasks killed externally. Metric with dag_id and task_id tagging.
`scheduler.orphaned_tasks.cleared`	`-`	Number of Orphaned tasks cleared by the Scheduler
`scheduler.orphaned_tasks.adopted`	`-`	Number of Orphaned tasks adopted by the Scheduler
`scheduler.critical_section_busy`	`-`	Count of times a scheduler process tried to get a lock on the critical section (needed to send tasks to the executor) and found it locked by another process.
`ti.start`	`ti.start.{dag_id}.{task_id}`	Number of started task in a given Dag. Similar to {job_name}_start but for task. Metric with dag_id and task_id tagging.
`ti.finish`	`ti.finish.{dag_id}.{task_id}.{state}`	Number of completed task in a given Dag. Similar to {job_name}_end but for task. Metric with dag_id and task_id tagging.
`dag.callback_exceptions`	`-`	Number of exceptions raised from Dag callbacks. When this happens, it means Dag callback is not working. Metric with dag_id tagging
`celery.task_timeout_error`	`-`	Number of `AirflowTaskTimeout` errors raised when publishing Task to Celery Broker.
`celery.execute_command.failure`	`-`	Number of non-zero exit code from Celery task.
`task_removed_from_dag`	`task_removed_from_dag.{dag_id}`	Number of tasks removed for a given Dag (i.e. task no longer exists in Dag). Metric with dag_id and run_type tagging.
`task_restored_to_dag`	`task_restored_to_dag.{dag_id}`	Number of tasks restored for a given Dag (i.e. task instance which was previously in REMOVED state in the DB is added to Dag file). Metric with dag_id and run_type tagging.
`task_instance_created`	`task_instance_created_{task_type}`	Number of tasks instances created for a given Operator. Metric with dag_id and run_type tagging.
`triggerer_heartbeat`	`-`	Triggerer heartbeats
`triggers.blocked_main_thread`	`-`	Number of triggers that blocked the main thread (likely due to not being fully asynchronous)
`triggers.failed`	`-`	Number of triggers that errored before they could fire an event
`triggers.succeeded`	`-`	Number of triggers that have fired at least one event
`asset.updates`	`-`	Number of updated assets
`asset.orphaned`	`-`	Number of assets marked as orphans because they are no longer referenced in Dag schedule parameters or task outlets
`asset.triggered_dagruns`	`-`	Number of Dag runs triggered by an asset update

Gauges

Name	Legacy Name	Description
`dagbag_size`	`-`	Number of Dags found when the scheduler ran a scan based on its configuration
`dag_processing.import_errors`	`-`	Number of errors from trying to parse Dag files
`dag_processing.total_parse_time`	`-`	Seconds taken to scan and import `dag_processing.file_path_queue_size` Dag files
`dag_processing.file_path_queue_size`	`-`	Number of Dag files to be considered for the next scan
`dag_processing.last_run.seconds_ago.{dag_file}`	`-`	Seconds since `{dag_file}` was last processed
`dag_processing.last_num_of_db_queries.{dag_file}`	`-`	Number of queries to Airflow database during parsing per `{dag_file}`
`scheduler.tasks.starving`	`-`	Number of tasks that cannot be scheduled because of no open slot in pool
`scheduler.tasks.executable`	`-`	Number of tasks that are ready for execution (set to queued) with respect to pool limits, Dag concurrency, executor state, and priority.
`scheduler.dagruns.running`	`-`	Number of DAGs whose latest DagRun is currently in the `RUNNING` state
`executor.open_slots`	`executor.open_slots.{executor_class_name}`	Number of open slots on executor. Legacy metric only emitted when multiple executors are configured.
`executor.queued_tasks`	`executor.queued_tasks.{executor_class_name}`	Number of queued tasks on executor. Legacy metric only emitted when multiple executors are configured.
`executor.running_tasks`	`executor.running_tasks.{executor_class_name}`	Number of running tasks on executor. Legacy metric only emitted when multiple executors are configured.
`pool.open_slots`	`pool.open_slots.{pool_name}`	Number of open slots in the pool.
`pool.queued_slots`	`pool.queued_slots.{pool_name}`	Number of queued slots in the pool.
`pool.running_slots`	`pool.running_slots.{pool_name}`	Number of running slots in the pool.
`pool.deferred_slots`	`pool.deferred_slots.{pool_name}`	Number of deferred slots in the pool.
`pool.scheduled_slots`	`pool.scheduled_slots.{pool_name}`	Number of scheduled slots in the pool.
`pool.starving_tasks`	`pool.starving_tasks.{pool_name}`	Number of starving tasks in the pool.
`triggers.running`	`triggers.running.{hostname}`	Number of triggers currently running for a triggerer (described by hostname).
`triggerer.capacity_left`	`triggerer.capacity_left.{hostname}`	Capacity left on a triggerer to run triggers (described by hostname).
`ti.scheduled`	`ti.scheduled.{queue}.{dag_id}.{task_id}`	Number of scheduled tasks in a given Dag.
`ti.queued`	`ti.queued.{queue}.{dag_id}.{task_id}`	Number of queued tasks in a given Dag.
`ti.running`	`ti.running.{queue}.{dag_id}.{task_id}`	Number of running tasks in a given Dag. As ti.start and ti.finish can run out of sync this metric shows all running tis.
`ti.deferred`	`ti.deferred.{queue}.{dag_id}.{task_id}`	Number of deferred tasks in a given Dag.
`edge_worker.connected`	`edge_worker.connected.{worker_name}`	Edge worker in state connected.
`edge_worker.maintenance`	`edge_worker.maintenance.{worker_name}`	Edge worker in state maintenance.
`edge_worker.jobs_active`	`edge_worker.jobs_active.{worker_name}`	Number of active jobs in an edge worker.
`edge_worker.concurrency`	`edge_worker.concurrency.{worker_name}`	Concurrency capacity in an edge worker.
`edge_worker.free_concurrency`	`edge_worker.free_concurrency.{worker_name}`	Available concurrency in an edge worker.
`edge_worker.num_queues`	`edge_worker.num_queues.{worker_name}`	Number of queues in an edge worker.
`edge_worker.heartbeat_count`	`edge_worker.heartbeat_count.{worker_name}`	Number heartbeats in an edge worker.

Timers

Name	Legacy Name	Description
`dagrun.dependency-check`	`dagrun.dependency-check.{dag_id}`	Milliseconds taken to check Dag dependencies
`task.duration`	`dag.{dag_id}.{task_id}.duration`	Milliseconds taken to run a task
`task.scheduled_duration`	`dag.{dag_id}.{task_id}.scheduled_duration`	Milliseconds a task spends in the Scheduled state, before being Queued
`task.queued_duration`	`dag.{dag_id}.{task_id}.queued_duration`	Milliseconds a task spends in the Queued state, before being Running
`dag_processing.last_duration`	`dag_processing.last_duration.{dag_file}`	Milliseconds taken to load the given Dag file
`dagrun.duration.success`	`dagrun.duration.success.{dag_id}`	Milliseconds taken for a DagRun to reach success state
`dagrun.duration.failed`	`dagrun.duration.failed.{dag_id}`	Milliseconds taken for a DagRun to reach failed state
`dagrun.schedule_delay`	`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
`scheduler.critical_section_query_duration`	`-`	Milliseconds spent running the critical section task instance query
`scheduler.scheduler_loop_duration`	`-`	Milliseconds spent running one scheduler loop
`dagrun.first_task_scheduling_delay`	`dagrun.{dag_id}.first_task_scheduling_delay`	Milliseconds elapsed between first task start_date and dagrun expected start
`collect_db_dags`	`-`	Milliseconds taken for fetching all Serialized Dags from DB
`kubernetes_executor.clear_not_launched_queued_tasks.duration`	`-`	Milliseconds taken for clearing not launched queued tasks in Kubernetes Executor
`kubernetes_executor.adopt_task_instances.duration`	`-`	Milliseconds taken to adopt the task instances in Kubernetes Executor
`ol.emit.attempts`	`ol.emit.attempts.{event_type}.{transport_type}`	Milliseconds taken by an attempt to emit an OpenLineage event.