​
Configuring Backend

  • GROUNDCOVER_ENDPOINT - Endpoint, the format is host:port.
    • host is required, also known as your inCloud_Site, it is part of the configuration provided to you by Groundcover when setting up the inCloud Managed backend.
    • port is optional, and defaults to the default OpenTelemetry gRPC port 4317.
  • GROUNDCOVER_API_KEY - API Key provided by Groundcover, refer to these docs for more info.

​
Adding a Destination to Odigos

Odigos makes it simple to add and configure destinations, allowing you to select the specific signals [traces/logs/metrics] that you want to send to each destination. There are two primary methods for configuring destinations in Odigos:

  1. Using the UI

Use the Odigos CLI to access the UI:

odigos ui
  1. Using kubernetes manifests

Save the YAML below to a file (e.g., destination.yaml) and apply it using kubectl:

kubectl apply -f destination.yaml

apiVersion: odigos.io/v1alpha1
kind: Destination
metadata:
  name: groundcover-example
  namespace: odigos-system
spec:
  data:
    GROUNDCOVER_ENDPOINT: <Groundcover inCloud Site>
  destinationName: groundcover
  secretRef:
    name: groundcover-secret
  signals:
  - TRACES
  - METRICS
  - LOGS
  type: groundcover

---
apiVersion: v1
data:
  GROUNDCOVER_API_KEY: <base64 Groundcover API Key>
kind: Secret
metadata:
  name: groundcover-secret
  namespace: odigos-system
type: Opaque
Grafana Cloud TempoHoneycomb