open-telemetry / open-telemetry/opentelemetry-java-instrumentation
Auto instrumentation Java Azure function app- Traceid propagation error
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.6k
- Forks
- 1.2k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 228
Description
Describe the bug
Java auto instrumentation for azure function app (both have different service name) calling from parent to child is always
- creating 2 spans under parent trace id but giving service name parent service
OR
- or creating 2 parent trace id under 2 different service name
Steps to reproduce
Otel auto instrumentation steps using jar file and tracecontext, baggage otel_propagator
Expected behavior
it should create 1 parent and 2 spans with respective service name
Actual behavior
2 spans for 1 trace and same service name
Javaagent or library instrumentation version
1.38
Environment
JDK:
OS:
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Java auto-instrumentation behavior with the jar, tracecontext, baggage, and otel_propagator across two Azure Function apps using version 1.38. Compare the parent and child spans and their service names. Done means one parent trace contains two child spans, with each span using its respective service name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, java
- Domain
- cloud, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100