open-telemetry / open-telemetry/opentelemetry-cpp-contrib
Exclude endpoint from otel
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 153
- Forks
- 184
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 26
Description
I have an nginx instance as reverse proxy running. This reverse proxy serves an endpoint (/v1/telemetry/) for other applications to send telemetry data.
I like to exclude this endpoint from sending telemetry data, since that's wasted space.
Thanks in advance!
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
No file, test, or entry point is identified in the issue. Start by locating how this project instruments or filters reverse-proxy endpoints, then determine where the /v1/telemetry/ path could be excluded. Done should mean that requests to this endpoint no longer generate telemetry while other endpoints continue to do so.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100