​
Configuring Backend

  • HYPERDX_API_KEY - HyperDX API Key.

Note: We handle the endpoint internally, so you don’t need to provide it.

  • The endpoint is in-otel.hyperdx.io:4317.

​
Adding a Destination to Odigos

Odigos makes it simple to add and configure destinations, allowing you to select the specific signals [traces/logs/metrics] that you want to send to each destination. There are two primary methods for configuring destinations in Odigos:

  1. Using the UI

Use the Odigos CLI to access the UI:

odigos ui
  1. Using kubernetes manifests

Save the YAML below to a file (e.g., destination.yaml) and apply it using kubectl:

kubectl apply -f destination.yaml

apiVersion: odigos.io/v1alpha1
kind: Destination
metadata:
  name: hyperdx-example
  namespace: odigos-system
spec:
  data: {}
  destinationName: hyperdx
  secretRef:
    name: hyperdx-secret
  signals:
  - TRACES
  - METRICS
  - LOGS
  type: hyperdx

---
apiVersion: v1
data:
  HYPERDX_API_KEY: <base64 HyperDX API Key>
kind: Secret
metadata:
  name: hyperdx-secret
  namespace: odigos-system
type: Opaque
HoneycombJaeger