Very happy to see the active work on this project!
I am eager to adopt opencensus/open-telemetry for the Kata Containers project, but we have a couple of particular needs that I'd like to see if we can add support for.
Background on use case
Kata is a container runtime, with part of the runtime infrastructure running on a host, kata-runtime, and the portion managing the container workload running within a virtual machine, kata-agent. Communication between the _kata-runtime and the kata-agent are carried out via gRPC running over vsock.
How we handle tracing today
Tracing is great, and we currently utilize open-tracing. We have to do several workarounds in order to get traces/metrics from both the kata-agent and the kata-runtime. Basically, in the guest we'd use a standard opencensus exporter and run socat to transfer from UDP->vsock, and then on the host run another instance of socat to take the data from vsock->UDP. This isn't very flexible, and makes tracing of the kata-agent very painful and error prone for our end users.
Ideal scenario
Opencensus/OpenTelemetry support for exporting to a vsock and receiving from both UDP and vsock. I'm happy to work with folks in the Kata community to get a PR in place, but wanted to get feedback from the open-telemetry and opencensus folks.
Very happy to see the active work on this project!
I am eager to adopt opencensus/open-telemetry for the Kata Containers project, but we have a couple of particular needs that I'd like to see if we can add support for.
Background on use case
Kata is a container runtime, with part of the runtime infrastructure running on a host, kata-runtime, and the portion managing the container workload running within a virtual machine, kata-agent. Communication between the _kata-runtime and the kata-agent are carried out via gRPC running over vsock.
How we handle tracing today
Tracing is great, and we currently utilize open-tracing. We have to do several workarounds in order to get traces/metrics from both the kata-agent and the kata-runtime. Basically, in the guest we'd use a standard opencensus exporter and run socat to transfer from UDP->vsock, and then on the host run another instance of socat to take the data from vsock->UDP. This isn't very flexible, and makes tracing of the kata-agent very painful and error prone for our end users.
Ideal scenario
Opencensus/OpenTelemetry support for exporting to a vsock and receiving from both UDP and vsock. I'm happy to work with folks in the Kata community to get a PR in place, but wanted to get feedback from the open-telemetry and opencensus folks.