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
Workaround: inject an attribute on every span and configure these as dimensions in the service-graph and span-metrics processor. This could be done in the application or by the tracing pipeline.
Downside: doing this in the instrumentation risks missing some spans --> these won't have a tenant ID and won't be counted.
Additional context
Implementation notes: we already inject a label in the registry
I think we just add some extra code here: if the config setting is active add another externalLabel which contains the value of tenant.
This will automatically add it to all metrics generated for that tenant.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Scenario:
Describe the solution you'd like
Tempo gets a configuration option to add the tenant ID as metric label to all generated metrics.
It would have to be a setting on the registry, something like:
Or maybe:
Describe alternatives you've considered
Workaround: inject an attribute on every span and configure these as
dimensions
in the service-graph and span-metrics processor. This could be done in the application or by the tracing pipeline.Downside: doing this in the instrumentation risks missing some spans --> these won't have a tenant ID and won't be counted.
Additional context
Implementation notes: we already inject a label in the registry
tempo/modules/generator/registry/registry.go
Lines 101 to 102 in d94e1f2
I think we just add some extra code here: if the config setting is active add another
externalLabel
which contains the value oftenant
.This will automatically add it to all metrics generated for that tenant.
The text was updated successfully, but these errors were encountered: