Skip to content

Docs: add missing metrics to metric tables#64046

Open
potiuk wants to merge 1 commit intoapache:mainfrom
potiuk:docs-add-missing-metrics
Open

Docs: add missing metrics to metric tables#64046
potiuk wants to merge 1 commit intoapache:mainfrom
potiuk:docs-add-missing-metrics

Conversation

@potiuk
Copy link
Member

@potiuk potiuk commented Mar 21, 2026

Add missing metrics to the documentation metric tables including deadline alerts, edge worker counters, OpenLineage metrics, executor adopt durations, and other recently added metrics.


Was generative AI tooling used to co-author this PR?
  • Yes — Claude Code (Claude Opus 4.6)

Generated-by: Claude Code (Claude Opus 4.6) following the guidelines

``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.
``ol.event.size.{event_type}.{operator_name}`` ``-`` Size in bytes of an OpenLineage event by event type and operator.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this not sorted alphabetically?

``deadline_alerts.deadline_missed`` ``-`` Number of deadline alerts that fired because a Dag run missed its deadline
``deadline_alerts.deadline_not_missed`` ``-`` Number of deadline records deleted because the Dag run finished before the deadline
``ol.emit.failed`` ``-`` Number of failed OpenLineage event emit attempts
``edge_worker.heartbeat_count`` ``edge_worker.heartbeat_count.{worker_name}`` Number heartbeats in an edge worker.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where is this generated from? Shall it really contain provider specific metrics in the docs in core?
Same with ecs_executor below...

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good question - those are define in a shared metrics observability library - and possibly we should have a mechanism (similar to configuration) to define them and pull them in the provider's docs:

@dstandish @xBis7 @kacpermuda @mobuchowski ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants