Checkly

Getting Started

Configuring Destination Fields

Supported Signals:

✅ Traces ❌ Metrics ❌ Logs ❌ Profiles

CHECKLY_ENDOINT string : OTLP gRPC Endpoint. The format is host:port, host is required, port is optional and defaults to the default OTLP gRPC port 4317.
- This field is required
CHECKLY_API_KEY string : API Key.
- This field is required

Odigos will only filter and export traces to Checkly if their trace_state includes the tag checkly="true", which is added by a Checkly SDK.

Adding Destination to Odigos

There are two primary methods for configuring destinations in Odigos:

Using the UI

Use the Odigos CLI to access the UI

odigos ui

Click on Add Destination, select Checkly and follow the on-screen instructions

Using Kubernetes manifests

Save the YAML below to a file (e.g. checkly.yaml)

apiVersion: odigos.io/v1alpha1
kind: Destination
metadata:
  name: checkly-example
  namespace: odigos-system
spec:
  data:
    CHECKLY_ENDOINT: <OTLP gRPC Endpoint>
  destinationName: checkly
  secretRef:
    name: checkly-secret
  signals:
  - TRACES
  type: checkly

---

apiVersion: v1
data:
  CHECKLY_API_KEY: <Base64 API Key>
kind: Secret
metadata:
  name: checkly-secret
  namespace: odigos-system
type: Opaque

Apply the YAML using kubectl

kubectl apply -f checkly.yaml

Causely Chronosphere

Getting Started

Instrumentations

Odigos Pipeline

Destinations

Concepts

Contribution Guidelines

Getting Started

Configuring Destination Fields

Adding Destination to Odigos

Using the UI

Using Kubernetes manifests

​Getting Started

​Configuring Destination Fields

​Adding Destination to Odigos

Using the UI

Using Kubernetes manifests

Getting Started

Configuring Destination Fields

Adding Destination to Odigos