Skip to main content

ā€‹
Getting Started

bonree

ā€‹
Configuring Destination Fields

āœ… Traces āœ… Metrics āŒ Logs
  • BONREE_ENDPOINT string : OTLP HTTP Endpoint. APM controller address, obtained from the probe deployment page.
    • This field is required
  • BONREE_ACCOUNT_ID string : Account ID. Obtained from the probe deployment page.
    • This field is required
  • BONREE_ENVIRONMENT_ID string : Environment ID. The default environment does not need to be configured.
    • This field is optional

ā€‹
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 Bonree ONE and follow the on-screen instructions
Using Kubernetes manifests
1

Save the YAML below to a file (e.g. bonree.yaml)
apiVersion: odigos.io/v1alpha1
kind: Destination
metadata:
  name: bonree-example
  namespace: odigos-system
spec:
  data:
    BONREE_ENDPOINT: <OTLP HTTP Endpoint>
  destinationName: bonree
  # Uncomment the 'secretRef' below if you are using the optional Secret.
  # secretRef:
  #   name: bonree-secret
  signals:
  - TRACES
  - METRICS
  type: bonree

---

# The following Secret is optional. Uncomment the entire block if you need to use it.
# apiVersion: v1
# data:
#   BONREE_ACCOUNT_ID: <Base64 Account ID>
#   BONREE_ENVIRONMENT_ID: <Base64 Environment ID>
# kind: Secret
# metadata:
#   name: bonree-secret
#   namespace: odigos-system
# type: Opaque
2

Apply the YAML using kubectl
kubectl apply -f bonree.yaml
āŒ˜I