Hi @ciment , sorry I haven´t been able to get back to this issue as I was busy with other things.
This is not specific to EDOT Java, the instrumentation comes from the opentelemetry-java-instrumentation which EDOT inherits from.
As a next step I would suggest to
- modify the sample application to make it able to use the upstream opentelemetry-java-instrumentation java agent in place of EDOT Java
- open an issue with instructions how to reproduce in GitHub - open-telemetry/opentelemetry-java-instrumentation: OpenTelemetry auto-instrumentation and instrumentation libraries for Java · GitHub
- the expected/effective span name can be extraced from the agent logs when you set `OTEL_JAVAAGENT_DEBUG=true` environment variable, this allows to reproduce the issue without kibana (also upstream is vendor-agnostic so other contributors are unlikely to use the same backend as you here).
Given there is likely a gap/bug in the upstream opentelemetry instrumentation, the issue will need to be handled there anyway.