[Feature request] Support custom resource attributes for hyperdx-frontend's internal telemetry signals
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 9.9k
- Forks
- 471
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 117
Description
Problem Statement
Hyperdx allows overriding the service.name for Hyperdx's own telemetry by setting NEXT_PUBLIC_OTEL_SERVICE_NAME in the env vars (Although this is not clearly documented anywhere).
But afaik there is to specify additional resource attributes for the hyperdx frontend app. We would like to be able to set the following attributes: service.namespace, service.version, deployment.environment
Things that I have tried and did not work
I tried setting NEXT_PUBLIC_OTEL_SERVICE_NAMESPACE:xyz or OTEL_RESOURCE_ATTRIBUTES:service.namespace=xyz or NEXT_PUBLIC_OTEL_RESOURCE_ATTRIBUTES:service.namespace=xyz but I did not see those being added to the otel request payload for metrics/logs/traces.
Configuration
Version: 2.16.0
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 hyperdx-frontend telemetry configuration and the existing NEXT_PUBLIC_OTEL_SERVICE_NAME handling. Check how resource attributes reach metrics, logs, and traces, then verify that the requested service.namespace, service.version, and deployment.environment values are configurable and present in the telemetry payloads.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100