Skip to main content

​
Getting Started

hyperdx

​
Configuring Destination Fields

✅ Traces ✅ Metrics ✅ Logs
  • HYPERDX_API_KEY string : HyperDX API Key.
    • This field is required
  • HYPERDX_LOG_NORMALIZER boolean : Enable Log Normalizer. Enable HyperDX log normalization processor. This parses JSON from log bodies, infers severity levels, and normalizes log attributes for better querying.
    • This field is optional and defaults to True
We handle the endpoint internally, so you don’t need to provide it.
  • The endpoint is in-otel.hyperdx.io:4317

​
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 HyperDX and follow the on-screen instructions
Using Kubernetes manifests
1
Save the YAML below to a file (e.g. hyperdx.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
2
Apply the YAML using kubectl
kubectl apply -f hyperdx.yaml