open-telemetry / open-telemetry/opentelemetry-cpp-contrib
11#0: *26934686 Unable to get trace context when expanding tracecontext var, client: *.*.*.*, server: *_server, request: "GET /api/* HTTP/1.1", host: "*.*.*"
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 153
- Forks
- 184
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 26
Description
Hi Team, I find an error message in Nginx when I set opentelemetry off in http block
The error message is as follow:
9#0: *4 connect() failed (111: Connection refused) while connecting to upstream, client: *.*.*.*, server: *_server, request: "GET /api/* HTTP/1.1", upstream: "http://*.*.*.*:10001/hello", host: "*.*.*.*"
11#0: *26934686 Unable to get trace context when expanding tracecontext var, client: *.*.*.*, server: *_server, request: "GET /api/v1/address/default HTTP/1.1", host: "*.*.*"
is there any configuration i miss?
thank you!
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 reported Nginx error with opentelemetry off in the HTTP block and inspect how the tracecontext variable is expanded for the /api/v1/address/default request. Determine whether the configuration is expected to suppress this error and document the required configuration or a focused fix; no repository file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100