OpenTelemetry Collector on Kubernetes Environment
The OpenTelemetry Collector supports receiving and exporting Metrics, Logs, and Traces on the Kubernetes environment.
Basic OpenTelemetry Deployment on Docker Environments
When deploying OpenTelemetry Collector on a Kubernetes Environment, refer to Basic OpenTelemetry Integration on Kubernetes, a sample helm-values.yaml file for configuring OpenTelemetry to export logs, metrics, and traces to Kloudfuse.
Ensure that you use either https or http correctly, in conjunction with tls being enabled or disabled.
Basic OpenTelemetry Integration on Kubernetes
image:
repository: "otel/opentelemetry-collector-contrib"
config:
exporters:
debug:
verbosity: basic
otlphttp:
tls:
insecure: true # add only if you're using insecure communication
logs_endpoint: https://<REPLACE KFUSE ADDRESS>/ingester/otlp/v1/logs
metrics_endpoint: https://<REPLACE KFUSE ADDRESS>/ingester/otlp/metrics
traces_endpoint: https://<REPLACE KFUSE ADDRESS>/ingester/otlp/traces
extensions:
health_check: {}
memory_ballast:
size_in_percentage: 40
processors:
batch:
timeout: 10s
resourcedetection:
detectors:
- env
- eks
- ec2
- gcp
- aks
- azure
override: false
timeout: 2s
receivers:
otlp:
protocols:
grpc:
endpoint: ${env:MY_POD_IP}:4317
http:
cors:
allowed_origins:
- http://*
- https://*
endpoint: 0.0.0.0:4318
service:
extensions:
- health_check
pipelines:
logs:
exporters:
- otlphttp
processors:
- batch
- resourcedetection
receivers:
- otlp
metrics:
exporters:
- otlphttp
processors:
- batch
- resourcedetection
receivers:
- otlp
traces:
exporters:
- otlphttp
processors:
- batch
- resourcedetection
receivers:
- otlp
telemetry:
metrics:
address: ${MY_POD_IP}:8888
mode: daemonset
service:
enabled: true
nameOverride: otelcol
ports:
metrics:
enabled: true
otlp:
enabled: true
otlp-http:
enabled: true
presets:
kubernetesAttributes:
enabled: true
resources: {}yaml
