Standardize timer metrics to milliseconds and remove config #43975
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kaxil
added
the
airflow3.0:breaking
- Removes the `timer_unit_consistency` configuration option, standardizing all timer and timing metrics to milliseconds by default. - Updates metric loggers (e.g., Datadog, OpenTelemetry) to ensure uniform milliseconds-based reporting. - Cleans up related warnings! This is a follow-up of apache#43966 for main & Airflow 3
kaxil
force-pushed
the
follow-timer-unit
branch
from
636d1a1 to
8b824c6
Compare
ashb
approved these changes
Nov 14, 2024
2 tasks
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
timer_unit_consistencyconfiguration option, standardizing all timer and timing metrics to milliseconds by default.This is a follow-up of #43966 for main & Airflow 3
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.