Policies · Legacy policies

TrafficLog

Legacy access logging that references a logging backend declared on the Mesh.

Kuma

Behaviour per target

--to-latest v2 (2.x) converted

Output: MeshAccessLog

Outbound shape. conf.backend is a name that points into Mesh.spec.logging.backends, while MeshAccessLog declares the backend inline. The migrator indexes every Mesh in the input directory first and copies the matching backend into to[].default.backends[] (file → type: File, tcp → type: Tcp).

If the Mesh is not in the input set, or the name is not found, the policy is emitted without the backend and a warning names the backend you must write by hand. With no conf.backend, the Mesh defaultBackend is used.

The TrafficLog is what turns access logging on. The Mesh conversion does not generate a mesh-wide MeshAccessLog from spec.logging; this conversion is the only place a logging backend ends up in the output. See Meshes.

--to-latest v3 (3.0) converted

Output: MeshAccessLog

Same as v2. The source object is listed under "Delete Before Upgrading to 3.0".

Timeline

VersionChange
3.0No longer affects generated Envoy configuration.
3.0Removed from the resource registry. Mesh.spec.logging is removed too.

Source files