ā€‹
Getting Started

ā€‹
Configuring Destination Fields

  • OPSVERSE_USERNAME string : User.
    • This field is required
  • OPSVERSE_PASSWORD string : Password.
    • This field is required
  • OPSVERSE_LOGS_URL string : Logs Endpoint.
    • This field is required
  • OPSVERSE_METRICS_URL string : Metrics Endpoint.
    • This field is required
  • OPSVERSE_TRACES_URL string : Traces Endpoint.
    • 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 OpsVerse and follow the on-screen instructions

Using Kubernetes manifests
1

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

apiVersion: odigos.io/v1alpha1
kind: Destination
metadata:
  name: opsverse-example
  namespace: odigos-system
spec:
  data:
    OPSVERSE_LOGS_URL: <Logs Endpoint>
    OPSVERSE_METRICS_URL: <Metrics Endpoint>
    OPSVERSE_TRACES_URL: <Traces Endpoint>
    OPSVERSE_USERNAME: <User>
  destinationName: opsverse
  secretRef:
    name: opsverse-secret
  signals:
  - TRACES
  - METRICS
  - LOGS
  type: opsverse

---

apiVersion: v1
data:
  OPSVERSE_PASSWORD: <Base64 Password>
kind: Secret
metadata:
  name: opsverse-secret
  namespace: odigos-system
type: Opaque
2

Apply the YAML using kubectl

kubectl apply -f opsverse.yaml
New RelicOTLP gRPC