Skip to content

Commit e27586f

Browse files
Update docs/use-cases/observability/clickstack/example-datasets/kubernetes.md
Co-authored-by: Shaun Struwig <[email protected]>
1 parent f94d5d2 commit e27586f

File tree

1 file changed

+1
-1
lines changed
  • docs/use-cases/observability/clickstack/example-datasets

1 file changed

+1
-1
lines changed

docs/use-cases/observability/clickstack/example-datasets/kubernetes.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -254,7 +254,7 @@ helm repo add open-telemetry https://open-telemetry.github.io/opentelemetry-helm
254254

255255
### Deploy Kubernetes collector components {#deploy-kubernetes-collector-components}
256256

257-
To collect logs and metrics from both each node and the cluster itself, we'll need to deploy two separate OpenTelemetry collectors, each with its own manifest. The two manifests provided - `k8s_deployment.yaml` and `k8s_daemonset.yaml` - work together to collect comprehensive telemetry data from your Kubernetes cluster.
257+
To collect logs and metrics from both the cluster itself and each node, we'll need to deploy two separate OpenTelemetry collectors, each with its own manifest. The two manifests provided - `k8s_deployment.yaml` and `k8s_daemonset.yaml` - work together to collect comprehensive telemetry data from your Kubernetes cluster.
258258

259259
- `k8s_deployment.yaml` deploys a **single OpenTelemetry Collector instance** responsible for collecting **cluster-wide events and metadata**. It gathers Kubernetes events, cluster metrics, and enriches telemetry data with pod labels and annotations. This collector runs as a standalone deployment with a single replica to avoid duplicate data.
260260

0 commit comments

Comments
 (0)