Skip to main content

ā€‹
Getting Started

groundcover To get an API Key, refer to these docs.

ā€‹
Configuring Destination Fields

āœ… Traces āœ… Metrics āœ… Logs
  • GROUNDCOVER_ENDPOINT string : Groundcover inCloud Site. 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 inCloud Managed. Port is optional, and defaults to the default OpenTelemetry gRPC port 4317.
    • This field is required
  • GROUNDCOVER_API_KEY string : Groundcover API Key.
    • This field is required

ā€‹
Adding Destination to Odigos

There are two primary methods for configuring destinations in Odigos:
Using the UI
1

Use the Odigos CLI to access the UI
odigos ui
2

Click on Add Destination, select Groundcover inCloud and follow the on-screen instructions
Using Kubernetes manifests
1

Save the YAML below to a file (e.g. groundcover.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
2

Apply the YAML using kubectl
kubectl apply -f groundcover.yaml