open-telemetry / open-telemetry/opentelemetry-cpp-contrib
Allow extra resource attributes to be added to traces from apache / nginx
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 153
- Forks
- 184
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 26
Description
Is your feature request related to a problem?
Yes, we use elasticsearch as APM tool, where our corporate expects certain resource attributes to be available on the trace so that the trace is delegated to the correct team. Currently all our traces are dropped
Describe the solution you'd like
Give the option to add resource attributes through the apache / nginx config
Describe alternatives you've considered
Add an OpenTelemetry collector in between, which is a lot of extra infra which should not be required for elasticsearch
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 locating the Apache and Nginx configuration entry points that create or export traces. Determine how configuration-defined resource attributes are represented, then verify that the configured attributes appear on exported traces without requiring an OpenTelemetry Collector.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- apache, nginx
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100