Alex Kormukhin
Alex Kormukhin
I mean hardcoded [exception.printStackTrace(printWriter)](https://github.com/open-telemetry/opentelemetry-java/blob/16be81aed803e15694de29c9cea25f7bcf4d77c1/sdk/trace/src/main/java/io/opentelemetry/sdk/trace/internal/data/ImmutableExceptionEventData.java#L68) in jaeger and otel span exporter:   We use manual instrumentation, not javaagent instrumentation ([spring sleuth](https://github.com/spring-cloud/spring-cloud-sleuth) with [otel](https://github.com/spring-projects-experimental/spring-cloud-sleuth-otel)). How can we customize that?
Directly via addEvent(String name, Attributes attributes)? Ok. Thanks.
Oh, we can't replace recordException calls to addEvent with third party instrumentation:  So customization on opentelemetry SDK level is very useful. > If you could prototype a concrete proposal,...
Consul token query parameter deprecated in Consul 1.17 #809
This feature is stopper for us for migration from zipkin. Zipkin can find by tags across all services:  We use elasticsearch as storage backend.