Skip to main content

​
Getting Started

signalfx

​
Configuring Destination Fields

❌ Traces ✅ Metrics ❌ Logs
  • SIGNALFX_ACCESS_TOKEN string : Access Token. The authentication token provided by Splunk Observability Cloud.
    • This field is required
  • SIGNALFX_REALM string : Realm. The SignalFx realm where your data will be sent (e.g., us0, us1, eu0).
    • This field is required
  • SIGNALFX_CA_PEM string : CA Certificate (PEM). Optional CA certificate in PEM format for TLS verification.
    • This field is optional
  • SIGNALFX_INSECURE_SKIP_VERIFY boolean : Skip TLS Verification. If enabled, TLS certificate verification will be skipped. Not recommended for production.
    • 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 SignalFx and follow the on-screen instructions
Using Kubernetes manifests
1
Save the YAML below to a file (e.g. signalfx.yaml)
apiVersion: odigos.io/v1alpha1
kind: Destination
metadata:
  name: signalfx-example
  namespace: odigos-system
spec:
  data:
    SIGNALFX_REALM: <Realm>
    # Note: The commented fields below are optional.
    # SIGNALFX_INSECURE_SKIP_VERIFY: <Skip TLS Verification>
  destinationName: signalfx
  # Uncomment the 'secretRef' below if you are using the optional Secret.
  # secretRef:
  #   name: signalfx-secret
  signals:
  - METRICS
  type: signalfx

---

# The following Secret is optional. Uncomment the entire block if you need to use it.
# apiVersion: v1
# data:
#   SIGNALFX_ACCESS_TOKEN: <Base64 Access Token>
#   SIGNALFX_CA_PEM: <Base64 CA Certificate (PEM)>
# kind: Secret
# metadata:
#   name: signalfx-secret
#   namespace: odigos-system
# type: Opaque
2
Apply the YAML using kubectl
kubectl apply -f signalfx.yaml