You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The DD_DOGSTATSD_MAPPER_PROFILES config used by the Airflow integration is missing the queued_duration metric, and mishandles task_instance_created past 2.6.3.
Queued duration
The dag.<dag_id>.<task_id>.queued_duration looks to have been introduced in Airflow 2.7.0, and the DogStatsD mapper profile provided on the Integrations page is missing its entry.
As a result, it's exploding the number of metrics (+3k in my case).
I suggest adding the following entry
The
DD_DOGSTATSD_MAPPER_PROFILES
config used by the Airflow integration is missing thequeued_duration
metric, and mishandlestask_instance_created
past 2.6.3.Queued duration
The
dag.<dag_id>.<task_id>.queued_duration
looks to have been introduced in Airflow 2.7.0, and the DogStatsD mapper profile provided on the Integrations page is missing its entry.As a result, it's exploding the number of metrics (+3k in my case).
I suggest adding the following entry
Task instance created
From version 2.6.3 to 2.7.0, the counter the task instance created metric changed format:
This results in 1 metric per operator, which makes it hardly usable.
The current mapping is
which could perhaps be
to handle both versions ?
Would it be worth adding a disclaimer, warning the user that the mapping was created for version X ?
The text was updated successfully, but these errors were encountered: