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
| tempo.overrides | object |`{"defaults":{},"per_tenant_override_config":"/conf/overrides.yaml"}`| The standard overrides configuration section. This can include a `defaults` object for applying to all tenants (not to be confused with the `global` property of the same name, which overrides `max_byte_per_trace` for all tenants). For an example on how to enable the metrics generator using the `overrides` object, see the 'Activate metrics generator' section below. Refer to [Standard overrides](https://grafana.com/docs/tempo/latest/configuration/#standard-overrides) for more details. |
77
+
| tempo.overrides.defaults | object |`{}`| Default config values for all tenants, can be overridden by per-tenant overrides. If a tenant's specific overrides are not found in the `per_tenant_overrides` block, the values in this `default` block will be used. Configs inside this block should follow the new overrides indentation format |
78
+
| tempo.overrides.per_tenant_override_config | string |`"/conf/overrides.yaml"`| Path to the per tenant override config file. The values of the `per_tenant_overrides` config below will be written to the default path `/conf/overrides.yaml`. Users can set tenant-specific overrides settings in a separate file and point per_tenant_override_config to it if not using the per_tenant_overrides block below. |
79
+
| tempo.per_tenant_overrides | object |`{}`| The `per tenant` aka `tenant-specific` runtime overrides. This allows overriding values set in the configuration on a per-tenant basis. Note that *all* values must be given for each per-tenant configuration block. Refer to [Runtime overrides](https://grafana.com/docs/tempo/latest/configuration/#runtime-overrides) and [Tenant-Specific overrides](https://grafana.com/docs/tempo/latest/configuration/#tenant-specific-overrides) documentation for more details. |
78
80
| tempo.pullPolicy | string |`"IfNotPresent"`||
79
81
| tempo.querier | object |`{}`| Configuration options for the querier. Refers to: https://grafana.com/docs/tempo/latest/configuration/#querier|
80
82
| tempo.queryFrontend | object |`{}`| Configuration options for the query-fronted. Refers to: https://grafana.com/docs/tempo/latest/configuration/#query-frontend|
@@ -153,6 +155,13 @@ The command removes all the Kubernetes components associated with the chart and
153
155
154
156
A major chart version change indicates that there is an incompatible breaking change needing manual actions.
155
157
158
+
### From Chart versions < 1.19.0
159
+
* Breaking Change *
160
+
In order to reduce confusion, the overrides configurations have been renamed as below.
161
+
162
+
`global_overrides` => `overrides` (this is where the defaults for every tenant is set)
163
+
`overrides` => `per_tenant_overrides` (this is where configurations for specific tenants can be set)
164
+
156
165
### From Chart versions < 1.17.0
157
166
158
167
Please be aware that we've updated the Tempo version to 2.7, which includes some breaking changes
Copy file name to clipboardexpand all lines: charts/tempo/values.yaml
+18-7
Original file line number
Diff line number
Diff line change
@@ -65,10 +65,24 @@ tempo:
65
65
# search:
66
66
# concurrent_jobs: 2000
67
67
retention: 24h
68
-
# Global overrides
69
-
global_overrides:
68
+
# -- The standard overrides configuration section. This can include a `defaults` object for applying to all tenants (not to be confused with the `global` property of the same name, which overrides `max_byte_per_trace` for all tenants). For an example on how to enable the metrics generator using the `overrides` object, see the 'Activate metrics generator' section below. Refer to [Standard overrides](https://grafana.com/docs/tempo/latest/configuration/#standard-overrides) for more details.
69
+
overrides:
70
+
# -- Default config values for all tenants, can be overridden by per-tenant overrides. If a tenant's specific overrides are not found in the `per_tenant_overrides` block, the values in this `default` block will be used. Configs inside this block should follow the new overrides indentation format
71
+
defaults: {}
72
+
# metrics_generator:
73
+
# processors:
74
+
# - service-graphs
75
+
# - span-metrics
76
+
77
+
# -- Path to the per tenant override config file. The values of the `per_tenant_overrides` config below will be written to the default path `/conf/overrides.yaml`. Users can set tenant-specific overrides settings in a separate file and point per_tenant_override_config to it if not using the per_tenant_overrides block below.
70
78
per_tenant_override_config: /conf/overrides.yaml
71
-
overrides: {}
79
+
# -- The `per tenant` aka `tenant-specific` runtime overrides. This allows overriding values set in the configuration on a per-tenant basis. Note that *all* values must be given for each per-tenant configuration block. Refer to [Runtime overrides](https://grafana.com/docs/tempo/latest/configuration/#runtime-overrides) and [Tenant-Specific overrides](https://grafana.com/docs/tempo/latest/configuration/#tenant-specific-overrides) documentation for more details.
80
+
per_tenant_overrides: {}
81
+
# 'tenant-id':
82
+
# metrics_generator:
83
+
# processors:
84
+
# - service-graphs
85
+
# - span-metrics
72
86
73
87
# Tempo server configuration.
74
88
# Refers to: https://grafana.com/docs/tempo/latest/configuration/#server
0 commit comments