Skip to content

Conversation

@jscheffl
Copy link
Contributor

As I was (together with @kaxil ) taking a look to the Scarf reports I saw some minor improvements we can have for the collected metrics:

  1. We are not actually interested in the (exact) Python version but Major.Minor is sufficient. Too preceise metrics are not getting a good report
  2. Same for DB Version. Major+Minor is sufficient
  3. Count of DAGs, Timetables and Plugins is also too precise, made a set of buckets as the Rough number is what we want to know

I think we are atm cutting the 2.10 release but I hope somehow we get it it, if not then 2.10.2 :-D

@jscheffl jscheffl added this to the Airflow 2.10.1 milestone Aug 30, 2024
@jscheffl jscheffl requested a review from kaxil August 30, 2024 15:23
@boring-cyborg boring-cyborg bot added the area:webserver Webserver related Issues label Aug 30, 2024
@jscheffl jscheffl merged commit 0f5c25b into apache:main Aug 30, 2024
@utkarsharma2 utkarsharma2 added the type:misc/internal Changelog: Misc changes that should appear in change log label Aug 30, 2024
@jedcunningham
Copy link
Member

I'm curious why we didn't do buckets for the other counts too - flask blueprints and appbuilder views/menu items? Just that we don't think we will have that wide of a range to begin with?

I think the current buckets make sense for DAGs, but not so much for plugins and timetables. We loose basically all granularity.

@kaxil
Copy link
Member

kaxil commented Sep 2, 2024

Fair point @jedcunningham - feel free to PR tour change

@jscheffl jscheffl deleted the feature/make-scarf-reporting-buckets branch October 5, 2025 07:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:webserver Webserver related Issues type:misc/internal Changelog: Misc changes that should appear in change log

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants