You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Global labels can have high cardinality when used for RUM. They are not currently part of aggregated metrics since #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.
@b2ronn due to an often expected high cardinality in RUM global labels, we would need to find a different solution than just adding global labels as an aggregation dimension. This can also be a challenge for non-RUM setups, and we are thinking about a more global solution to this. But the task is not currently scheduled for implementation and will likely not be part of the next minor versions.
As an alternative, it may be worth to consider adding the capability for the admin of the APM server to define the list of permitted global labels for "rum-js," "js-base," "android/java," "iOS/swift"?
Global labels can have high cardinality when used for RUM. They are not currently part of aggregated metrics since #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 elastic/observability-docs#3877
The text was updated successfully, but these errors were encountered: