Policies · Mesh* policies
MeshAccessLog
Access logging for inbound and outbound traffic to file, TCP or OpenTelemetry backends.
Behaviour per target
Output: MeshAccessLog
from[]→rules[], with a<name>-outboundsplit whento[]is also present.- An inline
openTelemetry.endpointis reported: deprecated in 2.14, removed in 3.0. Define a MeshOpenTelemetryBackend and reference it withbackendRef(labels only, system namespace). The warning says not to switch while any control plane or data plane runs below 2.14. openTelemetry.attributes[].keyvalues that 2.14 rejects (reservedotel.prefix, non-lowercase, placeholders) are reported.
Output: MeshAccessLog, MeshOpenTelemetryBackend
v2 rewrites, plus each inline openTelemetry.endpoint is replaced by
backendRef: {kind: MeshOpenTelemetryBackend, labels: {kuma.io/display-name: <name>-otel}}
and a matching MeshOpenTelemetryBackend is generated (in the system namespace on
Kubernetes, see Meshes; protocol grpc). Apply
the backend before the policy. Allowed to[].targetRef.kind:
Mesh, MeshService, MeshExternalService, MeshMultiZoneService, MeshHTTPRoute.
Timeline
| Version | Change |
|---|---|
| 2.10 | rules[] API added; from[] deprecated. |
| 2.14 | Inline openTelemetry.endpoint deprecated; attribute keys validated. |
| 3.0 | from and the inline OpenTelemetry endpoint removed. |
Related topics
- Observability — Metrics, tracing and access logs from Mesh fields and legacy policies to MeshMetric, MeshTrace, MeshAccessLog and MeshOpenTelemetryBackend.
- Policy targeting — Which targetRef kinds each policy accepts at each position on 2.14 and 3.0, labels-only selection, policy roles, and control-plane-owned labels.