open-telemetry / open-telemetry/opentelemetry-cpp-contrib
Gathering ephemeral port and source ip from module
Open
Nobody has claimed this yet.
Webserver
- Dominant language
- Python
- Stars
- 153
- Forks
- 184
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 26
Description
I am using the otel-webserver-module and need to gather networking informations from the NGINX proxy. If the proxy acts as a reverse proxy, I need to see which ephemeral port and source IP the NGINX proxy used to connect to the effective page/backend.
Is there any possibility for that?
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 with the otel-webserver-module documentation linked in the issue and inspect how the NGINX reverse-proxy request context is exposed. Determine whether the module can access the upstream ephemeral port and source IP; done should be a clear feasibility result or a defined implementation path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100