OpenTelemetry

Ingest and visualize OTEL data with groundcover

groundcover supports ingesting different data types in the OTEL format, displaying them natively in the platform. For more information see the following subpages:

Quick Start In a Kubernetes cluster

For more customization options see Traces & Logs, Metrics

The configuration below is meant to setup OTLP ingestion from a a single service in an environment with a standard installation of groundcover.

Apply the following environment variables to the instrumented service to redirect all signals to groundcover's ingestion endpoint inside your cluster.

groundcover collects all logs inside your k8s cluster out of the box without the need for any additional setup, so in most cases ingesting OTLP logs from inside your Kubernetes cluster is not recommended as it will cause log duplications.

For this reason, the values below include the OTEL_LOGS_EXPORTER: none setting, which will instruct the OTEL SDK to not send any logs.

Not sure? Contact us on Slack!

groundcover versions from 1.8.245

env:
  - name: OTEL_EXPORTER_OTLP_ENDPOINT
    value: "http://groundcover-sensor.groundcover.svc.cluster.local:4318"
  - name: OTEL_EXPORTER_OTLP_PROTOCOL
    value: "http/protobuf"
  - name: OTEL_LOGS_EXPORTER
    value: "none"

groundcover versions before 1.8.245

For versions before 1.8.245, it is required to turn on custom-metrics to enable the OTLP metrics endpoint. See docs here.

env:
  - name: OTEL_EXPORTER_OTLP_TRACES_ENDPOINT
    value: "http://groundcover-sensor.groundcover.svc.cluster.local:4318/v1/traces"
  - name: OTEL_EXPORTER_OTLP_LOGS_ENDPOINT
    value: "http://groundcover-sensor.groundcover.svc.cluster.local:4318/v1/logs"
  - name: OTEL_EXPORTER_OTLP_METRICS_ENDPOINT
    value: "http://custom-metrics.groundcover.svc.cluster.local:8429/opentelemetry/api/v1/push"
  - name: OTEL_EXPORTER_OTLP_PROTOCOL
    value: "http/protobuf"
  - name: OTEL_LOGS_EXPORTER
    value: "none"

Last updated 4 days ago