Skip to content

Conversation

jonatan-ivanov
Copy link
Member

TL;DR: this is a polishing PR as long as micrometer-metrics/micrometer#6700 is not merged (1.16.0). If that will happen, tests will break without this change.

Details:
The Micrometer team is considering some improvements in the Observation API which involves changing the behavior of Observation.NOOP: micrometer-metrics/micrometer#6700
Observation.NOOP is not truly no-op right now, it does context propagation, we are trying to make it truly no-op in the PR above. The non-truly no-op version will still be used in certain scenarios (see NoopButScopeHandlingObservation). observation.isNoop() should be used for checking if an Observation is no-op or not instead of Observation.NOOP.

@jonatan-ivanov jonatan-ivanov added the status: waiting-for-triage An issue we've not yet triaged label Sep 5, 2025
@philwebb philwebb added type: task A general task and removed status: waiting-for-triage An issue we've not yet triaged labels Sep 9, 2025
@philwebb philwebb added this to the 3.4.x milestone Sep 9, 2025
@snicoll snicoll self-assigned this Sep 9, 2025
@snicoll snicoll modified the milestones: 3.4.x, 3.4.10 Sep 9, 2025
@snicoll
Copy link
Member

snicoll commented Sep 9, 2025

This is only used on main, moving accordingly.

@snicoll snicoll modified the milestones: 3.4.10, 4.0.0-M3 Sep 9, 2025
snicoll pushed a commit that referenced this pull request Sep 9, 2025
@snicoll snicoll closed this in 63360f3 Sep 9, 2025
@snicoll
Copy link
Member

snicoll commented Sep 9, 2025

Thanks @jonatan-ivanov!

@jonatan-ivanov jonatan-ivanov deleted the is-noop branch September 9, 2025 15:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: task A general task
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants