Brandon Johnson

@tigrannajaryan Does this make sense to you? I'll update the PR if you're good with it.

I imagine the interaction to be like this: 1. Agent connects and sends AgentDescription. available_components is specified with only the hash present. 2. If the hash mismatches what is known...

@tigrannajaryan If you don't have any objections with the above, I'll get started on updating the PR to capture what was discussed here.

That makes sense to me.

https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/35507 was for a hacky fix that can fail depending on the extension implementation. Ideally this would be fully supported by the core repo. Ideally, we'd implement method 2 here....

Just adding what I've found here real quick; I've done a quick benchmark to see the difference between an actual tracer impl, vs noop tracer, vs all tracing removed in...

@andykellr @tigrannajaryan Here's a rough draft of ComponentDetails, when you get a second to take a look.

@tigrannajaryan friendly bump on this

Looks like a link is broken unrelated to the changes in this PR, but this should be good for another look.

OK, so I dived into the code a bit, and it looks like there's a span created for each statement. So if I execute, say, 10 statements, I'll get 10...