Kubernetes

helm repo add open-telemetry https://open-telemetry.github.io/opentelemetry-helm-charts
helm repo update

# values-squasher.yaml
mode: daemonset

presets:
  logsCollection:
    enabled: true
  kubernetesAttributes:
    enabled: true
  kubeletMetrics:
    enabled: true

config:
  exporters:
    otlphttp/squasher:
      endpoint: https://ingest.squasher.ai
      headers:
        x-squasher-key: "sq_pk_your_api_key"

  service:
    pipelines:
      logs:
        exporters: [otlphttp/squasher]
      traces:
        exporters: [otlphttp/squasher]
      metrics:
        exporters: [otlphttp/squasher]

helm install otel-collector open-telemetry/opentelemetry-collector \
  -f values-squasher.yaml \
  --namespace monitoring \
  --create-namespace

# deployment.yaml
env:
  - name: OTEL_EXPORTER_OTLP_ENDPOINT
    value: "http://otel-collector.monitoring.svc:4317"
  - name: OTEL_SERVICE_NAME
    value: "my-service"

# values-squasher.yaml
config:
  processors:
    filter/errors:
      logs:
        log_record:
          - severity_number >= 17 # ERROR and above
  service:
    pipelines:
      logs:
        processors: [filter/errors]
        exporters: [otlphttp/squasher]

Configure Kubernetes telemetry for Squasher project <project_id>. Patch the OpenTelemetry Collector values with the kubernetesAttributes and kubeletMetrics presets, keep secrets out of manifests when possible, export logs, traces, and metrics over OTLP, then verify one pod appears on the Kubernetes page. Ask before changing cluster-wide collection.