Policies · Legacy policies
TrafficTrace
Legacy tracing that references a tracing backend declared on the Mesh.
Behaviour per target
Output: MeshTrace
Selector shape: selectors → spec.targetRef, conf → spec.default (MeshTrace has
no to[]). conf.backend is resolved against Mesh.spec.tracing.backends in the input
set and written inline: zipkin/datadog backends become spec.default.backends[],
sampling becomes sampling.overall. An unresolved backend is reported by name.
The TrafficTrace is what turns tracing on. The Mesh conversion does not generate a
mesh-wide MeshTrace from spec.tracing; this conversion is the only place a tracing
backend ends up in the output. See Meshes.
Output: MeshTrace
Same as v2. The source object is listed for deletion.
Timeline
| Version | Change |
|---|---|
| 3.0 | No longer affects generated Envoy configuration. |
| 3.0 | Removed from the resource registry. Mesh.spec.tracing is removed too. |
Related topics
- Legacy policies — The twelve source/destination policies Kuma 3.0 removes, how kuma-migrator maps their selectors and conf to the Mesh* successors, and the two it leaves to you.
- Observability — Metrics, tracing and access logs from Mesh fields and legacy policies to MeshMetric, MeshTrace, MeshAccessLog and MeshOpenTelemetryBackend.