Vince Foley
Vince Foley
In my mind, `telemetry` is a great place for this. It's the library that we're asking all other libraries to leverage to instrument themselves. I see is as the most...
Why wouldn't it belong in `telemetry`? I don't think there's much to this API really - it's not trying to _solve_ all the problems regarding context propagation, it's simply providing...
> one returns some modified state Exactly
The approach the last few of you point to is definitely workable, but it foregoes any solution that works "out of the box" New Relic agents try to wire these...
> it would be a lot more clear what's going on if the HTTP client did something like how Tesla supports middleware That's true but it doesn't seem within the...
> It seems like what you're proposing here is a more-generic way for libraries to register that they would like to be involved whenever another library has an opportunity to...
I'm thinking a bit about this again... It seemed like one major concern was that some systems might not want to "assume" that every outgoing call should pass the context...
My thought is that I'm hoping that this won't really be needed, we just need to stick to the guidance of static event names + dynamic metadata for further filtering...
Hello there! Saw this go by and wanted to offer a few considerations: * You might want to ask the other agent teams about this before merging. If I recall,...
Before we can determine if it's usable, we need to clarify what it'd be used for... Are we suggesting adopting this in individual projects that do tracing like Open Census...