IBM Instana - Odigos

Getting Started

Creating Account
Go to the 🔗 Website > Account and click Log In Obtaining Endpoint
Go to the 📖 Docs > Endpoints of the Instana backend otlp-acceptor and find your Endpoint Obtaining Agent Key
Go to your 📩 Email > Instana Login Details and copy Agent-Key

Configuring Destination Fields

Supported Signals:

✅ Traces ✅ Metrics ✅ Logs ❌ Profiles

INSTANA_ENDPOINT string : OTLP gRPC Endpoint. Domain name of the otlp-acceptor component of the Instana backend.
- This field is required
- Example: otlp-{color}-saas.instana.io
INSTANA_AGENT_KEY string : Agent Key. The agent key of the Instana for targeting the Instana backend.
- This field is required

For ingesting logs via OpenTelemetry, an add-on to the Instana license is required. It’s advisable to contact your IBM Sales representative to include this add-on in your account.

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 IBM Instana and follow the on-screen instructions

Using Kubernetes manifests

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

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

---

apiVersion: v1
data:
  INSTANA_AGENT_KEY: <Base64 Agent Key>
kind: Secret
metadata:
  name: instana-secret
  namespace: odigos-system
type: Opaque

Apply the YAML using kubectl

kubectl apply -f instana.yaml

HyperDX Jaeger

​Getting Started

​Configuring Destination Fields

​Adding Destination to Odigos

Using the UI

Using Kubernetes manifests

Getting Started

Configuring Destination Fields

Adding Destination to Odigos