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: content/en/docs/concepts/cluster-administration/system-traces.md
+15Lines changed: 15 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,6 +22,9 @@ with the gRPC exporter and can be collected and routed to tracing backends using
22
22
23
23
## Trace Collection
24
24
25
+
Kubernetes components have built-in gRPC exporters for OTLP to export traces, either with an OpenTelemetry Collector,
26
+
or without an OpenTelemetry Collector.
27
+
25
28
For a complete guide to collecting traces and using the collector, see
26
29
[Getting Started with the OpenTelemetry Collector](https://opentelemetry.io/docs/collector/getting-started/).
27
30
However, there are a few things to note that are specific to Kubernetes components.
@@ -47,6 +50,16 @@ service:
47
50
exporters: [logging]
48
51
```
49
52
53
+
To directly emit traces to a backend without utilizing a collector,
54
+
specify the endpoint field in the Kubernetes tracing configuration file with the desired trace backend address.
55
+
This method negates the need for a collector and simplifies the overall structure.
56
+
57
+
For trace backend header configuration, including authentication details, environment variables can be used with `OTEL_EXPORTER_OTLP_HEADERS`,
58
+
see [OTLP Exporter Configuration](https://opentelemetry.io/docs/languages/sdk-configuration/otlp-exporter/).
59
+
60
+
Additionally, for trace resource attribute configuration such as Kubernetes cluster name, namespace, Pod name, etc.,
61
+
environment variables can also be used with `OTEL_RESOURCE_ATTRIBUTES`, see [OTLP Kubernetes Resource](https://opentelemetry.io/docs/specs/semconv/resource/k8s/).
62
+
50
63
## Component traces
51
64
52
65
### kube-apiserver traces
@@ -129,4 +142,6 @@ there are no guarantees of backwards compatibility for tracing instrumentation.
129
142
## {{% heading "whatsnext" %}}
130
143
131
144
* Read about [Getting Started with the OpenTelemetry Collector](https://opentelemetry.io/docs/collector/getting-started/)
145
+
* Read about [OTLP Exporter Configuration](https://opentelemetry.io/docs/languages/sdk-configuration/otlp-exporter/)
0 commit comments