Josh Suereth
Josh Suereth
This seems like the right path going forward. Now that these are all identifying, we CANNOT rely on joins for `scope`. :EDIT: or if we did, we'd need some kind...
+1 on semconv, also this walks into the "namespaced attributes" debate.
This seems to break the Histogram data model, particularly removing sum. Why not (when removing buckets) place the removed data into some single bucket or 'overflow' bucket? I'm not really...
Ah, so if you're removing buckets prometheus style, you have the benefit that buckets are just `less than` a threshod, I.e. they include counts from previous buckets. If you do...
@lmolkova @christophe-kamphaus-jemmic @adrielp - Regarding events vs. metrics a few thoughts: Overall: I think they can be complementary. We can define both, we should ensure metrics can be derived from...
I *do* think `Context` is a critical foundation of OTEL. Any method which records telemetry should have it (at least optionally) included. This is the only way, e.g. to allow...
> We don't need synchronization when interacting with context because it is immutable. Quick response to this: You need to get access to the current context. `Context` itself is immutable,...
This looks good to me.
Yes, we've debated it a bit. Leaving this open as enhancement but we'll need more information.
I agree about signal to noise, but I think the premise is at odds with our login design (and redesign coming). Primarily, `last` and `export` commands should show you all...