mirror of
https://github.com/aljazceru/kata-containers.git
synced 2026-01-02 14:04:22 +01:00
a9a0eccf33
Implement an openTelemetry custom exporter that sends trace spans to a VSOCK socket. A VSOCK-to-span converter (such as the Kata trace forwarder) needs to be running on the host to allow systems like Jaeger to capture the trace spans. By default, tracing is not enabled (meaning a NOP tracer is used). To activate tracing, set the `agent.kata.enable_tracing=true` in the configuration file. The type of tracing this change introduces is "static isolated" tracing. See [1] for further details. > **Note:** > > This change only provides the foundational changes for agent > tracing work. The feature is _not_ yet complete since it does > not yet show the correct trace hierarchy. Fixes: #60. [1] - https://github.com/kata-containers/agent/blob/master/TRACING.md Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
Trace Forwarder
Overview
The Kata Containers trace forwarder, kata-trace-forwarder, is a component
running on the host system which is used to support tracing the agent process
which runs inside the virtual machine.
The trace forwarder, which must be started before the agent, listens over VSOCK for trace data sent by the agent running inside the virtual machine. The trace spans are exported to an OpenTelemetry collector (such as Jaeger) running by default on the host.
Full details
Run:
$ cargo run -- --help