Skip to content

Remove stale metrics no longer emitted from the metrics registry#68945

Open
FrankYang0529 wants to merge 1 commit into
apache:mainfrom
FrankYang0529:remove-stale-metrics
Open

Remove stale metrics no longer emitted from the metrics registry#68945
FrankYang0529 wants to merge 1 commit into
apache:mainfrom
FrankYang0529:remove-stale-metrics

Conversation

@FrankYang0529

Copy link
Copy Markdown
Member

Remove the three orphaned entries from metrics_template.yaml:


Was generative AI tooling used to co-author this PR?
  • Yes (please specify the tool below)

  • Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
  • For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
  • When adding dependency, check compliance with the ASF 3rd Party License Policy.
  • For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

dag_processing.manager_stalls, dag_file_refresh_error, and collect_db_dags describe metrics
whose emission was removed in earlier refactors (apache#45729, apache#44972, apache#53918)

Signed-off-by: PoAn Yang <payang@apache.org>
@FrankYang0529 FrankYang0529 marked this pull request as ready for review June 24, 2026 12:51

@SameerMesiah97 SameerMesiah97 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I searched for these metrics in main and I could find them being emitted anywhere. I do wonder why they were not removed from .yaml file? I want to make sure removing them from the registry won't impact any tooling that relies on the template rather than the emitted metrics themselves. This looks fine to me but let's wait for a maintiainer to weigh in.

@Lee-W Lee-W left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

make sense to me. probably also worth a quick confirm from @ashb @jedcunningham and @uranusjr (the original author of the PRs).

we can also add a prek hook to check. e.g., if we add or remove a metrics, we trigger this hook to compare the metric in the doc and in the code

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants