Support global labels for aggregated metrics for RUM
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 543
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 109
Description
Global labels can have high cardinality when used for RUM. They are not currently part of aggregated metrics since https://github.com/elastic/apm-server/pull/10624, to avoid causes for `overflow` buckets. This currently impacts apm data collected by the "rum-js", "js-base", "android/java", "iOS/swift" agents.
We should find a way to also support global labels for RUM.
Update the docs once this is completed, to undo the change in https://github.com/elastic/observability-docs/pull/3877
Contributor guide
Research direction
Start by reviewing the change in apm-server PR 10624 and the documentation change in observability-docs PR 3877 to understand the overflow-bucket constraint and the current RUM behavior. Determine a safe design for including global labels in aggregated RUM metrics, then update the documentation to undo the documented limitation and verify the affected rum-js, js-base, android/java, and iOS/swift agent cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100