Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change the way Micrometer LongTaskTimer is bridged #5338

Merged
merged 1 commit into from
Feb 18, 2022

Conversation

mateuszrzeszutek
Copy link
Member

I realized that the previous way of reporting LongTaskTimer measurements, the one using a histogram, was wrong. As the example from #5292 (comment) shows, for long running task you might want to set up a LongTaskTimer for currently running tasks and a separate Timer for ones that have already finished - so reporting metrics for finished tasks in LongTaskTimer would result in duplicate metrics; and would not show the durations of tasks in progress. I removed the OTel histogram usage from LongTaskTimer; now it only reports metrics for tasks in progress (which should be consistent with all other LongTaskTimer implementations).

@mateuszrzeszutek mateuszrzeszutek requested a review from a team February 10, 2022 14:12
@trask trask merged commit 6774ce5 into open-telemetry:main Feb 18, 2022
@mateuszrzeszutek mateuszrzeszutek deleted the long-task-timer branch March 3, 2022 12:09
RashmiRam pushed a commit to RashmiRam/opentelemetry-auto-instr-java that referenced this pull request May 23, 2022
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.

2 participants