Skip to main content

​
Getting Started

oracle

​
Configuring Destination Fields

✅ Traces ✅ Metrics ❌ Logs
  • ORACLE_ENDPOINT string : OTLP HTTP Endpoint. The data upload endpoint of the Oracle APM domain.
    • This field is required
  • ORACLE_DATA_KEY string : Data Key.
    • This field is required
  • ORACLE_DATA_KEY_TYPE string : Data Key Type. The type of the data key, relevant for Traces. Metrics are always authenticated with a private data key.
    • This field is required and defaults to private

​
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 Oracle Cloud and follow the on-screen instructions
Using Kubernetes manifests
1
Save the YAML below to a file (e.g. oracle.yaml)
apiVersion: odigos.io/v1alpha1
kind: Destination
metadata:
  name: oracle-example
  namespace: odigos-system
spec:
  data:
    ORACLE_DATA_KEY_TYPE: '<Data Key Type (default: private) (options: [private, public])>'
    ORACLE_ENDPOINT: <OTLP HTTP Endpoint>
  destinationName: oracle
  secretRef:
    name: oracle-secret
  signals:
  - TRACES
  - METRICS
  type: oracle

---

apiVersion: v1
data:
  ORACLE_DATA_KEY: <Base64 Data Key>
kind: Secret
metadata:
  name: oracle-secret
  namespace: odigos-system
type: Opaque
2
Apply the YAML using kubectl
kubectl apply -f oracle.yaml