[OpenLineage] feat: Add metrics for event_size and extraction time #37797
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
kacpermuda
force-pushed
the
feat/ol-add-metrics
branch
from
cb99f03 to
d1569fd
Compare
kacpermuda
commented
Feb 29, 2024
kacpermuda
commented
Feb 29, 2024
kacpermuda
commented
Feb 29, 2024
kacpermuda
force-pushed
the
feat/ol-add-metrics
branch
2 times, most recently
from
346d576 to
0335a47
Compare
kacpermuda
force-pushed
the
feat/ol-add-metrics
branch
from
0335a47 to
4b09593
Compare
mobuchowski
approved these changes
Mar 1, 2024
79 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.
Adding metrics. Event size (operator name scope, event type scope), extraction time (operator name scope, event type scope) and sending time (transport scope, event type scope).
^ 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.