Observability
First-party Go processes emit JSON logs to stdout or stderr. Chart-owned metric endpoints support Prometheus discovery. First-party processes export traces through their SDK and the sidecar collector installed by the DSX observability stack. Structured allow, deny, and dependency events never include credentials.
SPIRE server, controller-manager, and the optional local SPIRE agent expose
their native Prometheus metrics through chart-owned monitors. SPIRE
does not produce traces. SPIFFE CSI Driver, CSI node-driver-registrar, and
the socat proxy expose no native application telemetry. Their health checks,
container logs, and platform container metrics remain available.
The DSX sidecar collector configuration has a trace pipeline and no metrics
pipeline. dsx-token-fetcher, metadata-service, and
dsx-imds-network-setup export traces and do not expose application metrics.
Tracing adds the SDK and sidecar annotations shown below to chart-owned application Pods and the SPIRE server Pod. Repository-owned SPIRE server plugins inherit the injected server-container environment.
Pods that receive an identity container supply the same tracing annotations on their Pod template. For token-fetcher injection:
The service label selects SPIRE registration. The injection annotation selects the token fetcher through native admission policy. The audience annotation names the relying party for the requested SPIRE JWT-SVID and exchanged DSX JWT-SVID.
For KubeVirt IMDS injection, put them on the VM Pod template: