> ## 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.

# Chronosphere

> Configuring the Chronosphere backend (Managed)

### Getting Started

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

Chronosphere is a monitoring and observability platform that provides a scalable, reliable, and cost-effective way to collect, store, and analyze metrics and traces.
To send data from Odigos to Chronosphere, [you need to have an account with Chronosphere](https://chronosphere.io/demo-request/) and configure the Chronosphere destination in Odigos with the following details:

### Configuring Destination Fields

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

* **CHRONOSPHERE\_DOMAIN** `string` : Chronosphere Company Domain. Company domain in Chronosphere, can be found in the URL of the Chronosphere UI. For example, if your URL is `https://demo-sandbox.chronosphere.io/`, then your company domain is `demo-sandbox`
  * This field is required
* **CHRONOSPHERE\_API\_TOKEN** `string` : API Token. API token generated from your Chronosphere service account in the Chronosphere UI, you should login to your Chronosphere admin account click the `Platform` menu on the left side of the screen, then click `Service Accounts` and create a new service account
  * 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 `Chronosphere` and follow the on-screen instructions
  </Step>
</Steps>

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

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

    ```yaml theme={null}
    apiVersion: odigos.io/v1alpha1
    kind: Destination
    metadata:
      name: chronosphere-example
      namespace: odigos-system
    spec:
      data:
        CHRONOSPHERE_DOMAIN: <Chronosphere Company Domain>
      destinationName: chronosphere
      secretRef:
        name: chronosphere-secret
      signals:
      - TRACES
      - METRICS
      type: chronosphere

    ---

    apiVersion: v1
    data:
      CHRONOSPHERE_API_TOKEN: <Base64 API Token>
    kind: Secret
    metadata:
      name: chronosphere-secret
      namespace: odigos-system
    type: Opaque
    ```
  </Step>

  <Step>
    Apply the YAML using `kubectl`

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