> ## Documentation Index
> Fetch the complete documentation index at: https://docs.odigos.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Groundcover inCloud

> Configuring the Groundcover inCloud backend (Managed)

### Getting Started

<img src="https://d15jtxgb40qetw.cloudfront.net/groundcover.svg" alt="groundcover" className="not-prose h-20" />

To get an API Key, refer to [these docs](https://docs.groundcover.com/architecture/byoc/ingestion-endpoints#creating-an-ingestion-key).

### Configuring Destination Fields

<Accordion title="Supported Signals:">
  ✅ Traces
  ✅ Metrics
  ✅ Logs
  ❌ Profiles
</Accordion>

* **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**

<Steps>
  <Step>
    Use the [Odigos CLI](https://docs.odigos.io/cli/odigos_ui) to access the UI

    ```bash theme={null}
    odigos ui
    ```
  </Step>

  <Step>
    Click on `Add Destination`, select `Groundcover inCloud` and follow the on-screen instructions
  </Step>
</Steps>

##### **Using Kubernetes manifests**

<Steps>
  <Step>
    Save the YAML below to a file (e.g. `groundcover.yaml`)

    ```yaml theme={null}
    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
    ```
  </Step>

  <Step>
    Apply the YAML using `kubectl`

    ```bash theme={null}
    kubectl apply -f groundcover.yaml
    ```
  </Step>
</Steps>