Replies: 1 comment 1 reply
-
Since auto instrumentation is done on the https://github.com/open-telemetry/opentelemetry-java-instrumentation side, I believe some changes will need to be done there. Specifically, the OTel agent's logic for mapping an ILoggingEvent to an OTel SDK LogBuilder would need to either :
This could work with some sort of default set of JSON providers. Or optionally OTel would need to provide some way to configure additional JSON providers I don't think there's anything that can be done in the logstash-logback-encoder repository for this without changes on the opentelemetry-java-instrumentation side. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I'm considering the adoption of the OpenTelemetry standard and I'm planning to use the "magic" logstash-logback-encoder in order to emit logs.
Anyway, at the moment, the logback auto instrumentation provided by the OpenTelemetry libs doesn't support any encoder:
the javaagent instruments the logback Logger interface and captures the logs regardless of what appender or encoder you are using
I have implemented a little PoC and started a thread about this issue on the OpenTelemetry github:
open-telemetry/opentelemetry-java-instrumentation#5496
Considering that OpenTelemetry is going to be the observability "de-facto" standard in the CNCF , it would be very useful if the logstash-logback-encoder could be supported for auto instrumentation.
Beta Was this translation helpful? Give feedback.
All reactions