You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: keps/sig-instrumentation/2831-kubelet-tracing/README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -106,7 +106,7 @@ From there, OpenTelemetry trace data can be exported to a tracing backend of cho
106
106
specified within `kubernetes/component-base` with the default URL to make the kubelet send its spans to the collector.
107
107
Alternatively, I can point the kubelet at an OpenTelemetry collector listening on a different port or URL if I need to.
108
108
109
-
#### Continuous Trace Collection
109
+
#### Continuous trace collection
110
110
111
111
As a cluster administrator or cloud provider, I would like to collect gRPC and HTTP trace data from the transactions between the API server and the
112
112
kubelet and interactions with a node's container runtime (Container Runtime Interface) to debug cluster problems. I can set the `SamplingRatePerMillion`
@@ -115,7 +115,7 @@ debug, I can search span metadata or specific nodes to find a trace which displa
115
115
The sampling rate for trace exports can be configured based on my needs. I can collect each node's kubelet trace data as distinct tracing services
0 commit comments