Skip to main content

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.

ā€‹
Getting Started

chronosphere 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 and configure the Chronosphere destination in Odigos with the following details:

ā€‹
Configuring Destination Fields

āœ… Traces āœ… Metrics āŒ Logs
  • 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
1
Use the Odigos CLI to access the UI
odigos ui
2
Click on Add Destination, select Chronosphere and follow the on-screen instructions
Using Kubernetes manifests
1
Save the YAML below to a file (e.g. chronosphere.yaml)
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
2
Apply the YAML using kubectl
kubectl apply -f chronosphere.yaml