Sabaev

Results 5 comments of Sabaev

`backgroundInactivityTimeout` miscounts on Android due to a clock that pauses in deep sleep

related to https://github.com/open-telemetry/opentelemetry-android/issues/1364

`Clock.getDefault()` isn’t configurable; add platform-aware selection & override hooks

Here is the approach I’m currently using: ## Shared Clock abstraction. In our internal project we expose our own Clock interface, accessible via a static companion object. This allows us...

`Clock.getDefault()` isn’t configurable; add platform-aware selection & override hooks

For monotonic time on Android, SystemClock.elapsedRealtimeNanos() is generally a better choice than System.nanoTime(). The reason: System.nanoTime() does not include time spent in deep sleep, so duration calculations (timeouts, background intervals,...

AttributeMap does not respect last-value-wins semantics for duplicate keys (SpanBuilder.setAttribute vs Attributes.builder)

@trask Sure, I’ll give it a try 🙂

AttributeMap does not respect last-value-wins semantics for duplicate keys (SpanBuilder.setAttribute vs Attributes.builder)

I investigated the inconsistent last-value-wins behavior in OpenTelemetry Java. The root cause is that `AttributesMap` stores attributes in a `HashMap