You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In an eBPF program I'm collecting information about certain Linux kernel tracepoint events into a map-based histogram. As these are high-count tracepoints it most probably doesn't make sense to do the histogram calculations in user space as this would require sending large numbers of events from kernel to user space.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In an eBPF program I'm collecting information about certain Linux kernel tracepoint events into a map-based histogram. As these are high-count tracepoints it most probably doesn't make sense to do the histogram calculations in user space as this would require sending large numbers of events from kernel to user space.
After reading the OTel documentation, and https://opentelemetry.io/docs/specs/otel/metrics/api/#asynchronous-instrument-api and https://opentelemetry.io/docs/specs/otel/metrics/api/#histogram in particular, there doesn't seem to be an async version provided. It appears as if the assumption was that normally histograms only appear as aggregating other instrument measures, but not as "proxies" for already calculated histograms.
How do I implement an "async" histogram using the otel Go SDK?
Beta Was this translation helpful? Give feedback.
All reactions