Description

This issue will track the work of adding OpenTelemetry tracing to CRI-O as well as the ability to export tracing data to a back-end of choice through a vendor-agnostic OpenTelemetry Collector.

The goal is to more easily detect and diagnose problems as well as improve performance of CRI-O. Tracing tracks and observes service requests as they flow through a system by collecting data as requests go from one service to another. It's possible, then, to pinpoint bugs and bottlenecks or other issues that can impact overall system performance. Tracing provides the story of an end-to-end request that is difficult to get otherwise.

@husky-parul (Parul) and I (@sallyom) will be implementing this. We will work with others to determine where best to add spans to collect traces.

To begin with, we'll add traces for:

• podSandbox creation
• ListContainers

Please add in comments points in code where it would be useful to gain more information through traces.