John Watson

> One more option to always include manual spans is to use InstrumentationLibrary.Name: if it does not start with `io.opentelemetry`, then return `RECORD` how would you implement that with a...

Do you have some ideas on what else we could provide for client/server examples? Or, is the http example enough?

> @jkwatson the simplest (and cheapest) model would be a single span for a logical HTTP request with all of the data listed above added as events. Would that model...

> > If more than one instrumentation library considers themselves the logical HTTP client, how should that be handled? > > Ideally, the higher level client should presume that instrumentation...

FYI, as written, `otel.experimental.sdk.enabled` is actually a java system property, not an env var. The corresponding env var is `OTEL_EXPERIMENTAL_SDK_ENABLED`.

It would be really great if this didn't require a workaround. I'm in this position, as well, as we have both the stage & production remotes, named as such, and...

Is there a way to have it also respect the standard heroku `--remote xyz` method of selecting a heroku app? I don't know much about how these plugins work at...

Hi @skonto. This is definitely something that I am interested in, being at verta. Have you thought about what kind of metric aggregations would be relevant for model monitoring, and...

I think the interesting new work would be in model performance, and not necessarily in the operational performance, which I think would probably fall understand standard observability-style metrics. With regards...

> > I'm not sure OTel itself really has facilities for "time windowed" cumulative histograms right now... there might be an opportunity to make a proposal to fulfill that need....