Trask Stalnaker

@bogdandrutu is this what you're looking for? https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/logs/api.md#enabled

Update: @austinlparker is looking at getting our Buffer account transferred to CNCF and added to the community assets. I can hook up the Zapier automation. @svrnm can you check this?...

@mx-psi @open-telemetry/configuration-maintainers what do you think of moving this meta issue to https://github.com/open-telemetry/opentelemetry-configuration? EDIT oops! I see @jack-berg just transferred it here

I think this may be a language-ecosystem thing. The JVM has been emitting "process cpu time" for almost 2 decades, so Java users very much expect this to be emitted...

to me, I would like "natively instrumented library" to mean that everyone who is using that library who is also using the OpenTelemetry SDK will get telemetry from the library...

> I'm supportive of recording the (terminal) exception on the span attributes and introducing `Span.End(Exception | Error)` +1

> does that mean that projects that aren't using OTel logging are simply not going to be able to observe exceptions? this is not true projects that aren't sending OTLP...

One downside to including `exception.message` in span status description is that we've seen a couple of cases in Java instrumentation where `exception.message` (unfortunately) contains sensitive data: - https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues/8422 - https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues/3039...

hi @greatvovan! I was able to reproduce your findings and it took me a while, but I finally found where the logs go in azure databricks 😅 and saw this:...

> I think you should be able to exclude com.azure:azure-core-http-netty so if this was a maven project, here's what I would do: ``` com.azure azure-monitor-opentelemetry-exporter 1.0.0-beta.29 com.azure azure-core-http-netty com.azure azure-core-http-okhttp...