opensearch-project / opensearch-project/OpenSearch
[Telemetry-otel] Different exporters/samplers should have configurable settings
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 13.7k
- Forks
- 3k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 108
Description
Is your feature request related to a problem? Please describe.
Different exporters/samplers should have various settings like timeout, endpoint as configurable through cluster settings or system settings.
Describe the solution you'd like
Add support for auto-configurable Telemetry sdk for system settings.
Describe alternatives you've considered
Check if we can provide the same support through cluster settings.
Additional context
Add any other context or screenshots about the feature request here.
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 investigating the Telemetry-otel implementation and how OpenSearch currently exposes system and cluster settings. Determine which exporter and sampler options need configuration and whether system settings or cluster settings are the appropriate mechanism. Done means the supported settings are defined, applied to the telemetry SDK, and covered by relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100