Alex Kormukhin

Results 5 comments of 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: ![image](https://user-images.githubusercontent.com/99888299/219030664-7cbbb037-6273-42ac-9a61-82b9da65a26c.png) ![image](https://user-images.githubusercontent.com/99888299/219033548-cc7a68bf-5334-43a2-80b9-c4209b7449c6.png) 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: ![image](https://user-images.githubusercontent.com/99888299/219694551-c5ec121c-8504-4271-8ed1-2b71d2ae19c0.png) 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: ![image](https://user-images.githubusercontent.com/99888299/219021939-3a0ad1cf-5bcd-4e8b-be49-65da93cf8933.png) We use elasticsearch as storage backend.