Skip to content

Conversation

@jonatan-ivanov
Copy link
Member

If you call the measure method of LongTaskTimer and check the duration, it's always in nanoseconds instead of the baseUnit.
It seems the original intention was using the base unit: 70925b3#diff-551e65260957b90931b406fcb647b39367c83d11aa8f07d3f388c667d60f8971R124
fixes gh-2947

If you call the measure method of LongTaskTimer and check the duration, it's always in nanoseconds instead of the baseUnit.
It seems the original intention was using the base unit: micrometer-metrics@70925b3#diff-551e65260957b90931b406fcb647b39367c83d11aa8f07d3f388c667d60f8971R124
fixes micrometer-metricsgh-2947
@jonatan-ivanov jonatan-ivanov changed the base branch from main to 1.7.x January 7, 2022 03:51
@shakuzen shakuzen merged commit fe43577 into micrometer-metrics:1.7.x Jan 7, 2022
@jonatan-ivanov jonatan-ivanov deleted the longtasktimer-measure-fix branch January 7, 2022 04:19
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.

LongTaskTimer always converts durations of measurements to nanos

2 participants