What is the problem you're trying to solve
containerd 1.6 will have OpenTelemetry spans, but they are added automatically around gRPC calls. There are a few areas we should have spans to make troubleshooting easier.
- The Go client's methods
- CRI
- GC operations
- HTTP calls around container image operations
Describe the solution you'd like
We need to first define our naming conversion based on https://github.com/open-telemetry/opentelemetry-specification/tree/main/specification/trace/semantic_conventions. After that we can update each component accordingly.
Additional context
No response
What is the problem you're trying to solve
containerd 1.6 will have OpenTelemetry spans, but they are added automatically around gRPC calls. There are a few areas we should have spans to make troubleshooting easier.
Describe the solution you'd like
We need to first define our naming conversion based on https://github.com/open-telemetry/opentelemetry-specification/tree/main/specification/trace/semantic_conventions. After that we can update each component accordingly.
Additional context
No response