Skip to content

Connected traces in the kubelet #113414

@dashpole

Description

@dashpole

What would you like to be added?

Right now, kubelet tracing produces disconnected spans for each CRI call:

Screen Shot 2022-10-25 at 4 13 34 PM

It would be helpful to add a parent span, in order to connect the CRI calls together (PoC):
Screen Shot 2022-10-26 at 5 05 01 PM

In order to do this, we need to:

Why is this needed?

Part of KEP kubernetes/enhancements#2831

Metadata

Metadata

Labels

kind/featureCategorizes issue or PR as related to a new feature.sig/instrumentationCategorizes an issue or PR as relevant to SIG Instrumentation.sig/nodeCategorizes an issue or PR as relevant to SIG Node.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions