Skip to main content

​
Getting Started

azuremonitor

​
Configuring Destination Fields

✅ Traces ✅ Metrics ✅ Logs
  • AZURE_MONITOR_CONNECTION_STRING string : Connection String. The Connection String is the recommended method for configuring the exporter, aligning with Azure Monitor’s best practices. If you don’t have a Connection String, you can create one in the Azure Portal (after creating an Application Insights resource).
    • This field is optional
  • AZURE_MONITOR_INSTRUMENTATION_KEY string : Instrumentation Key. Application Insights instrumentation key, which can be found in the Application Insights resource in the Azure Portal. While it is currently supported, its use is discouraged and it is slated for deprecation.
    • This field is optional
  • AZURE_MONITOR_ENDPOINT string : Endpoint. The endpoint URL where data will be submitted. While this option remains available, it is important to note that the use of the Connection String is recommended, as it encompasses the endpoint information. The direct configuration of the endpoint is considered to be on a deprecation path.
    • This field is optional
Do not configure the APPLICATIONINSIGHTS_CONNECTION_STRING environment variable. It will override this configuration!

​
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 Azure Monitor and follow the on-screen instructions
Using Kubernetes manifests
1

Save the YAML below to a file (e.g. azuremonitor.yaml)
apiVersion: odigos.io/v1alpha1
kind: Destination
metadata:
  name: azuremonitor-example
  namespace: odigos-system
spec:
  data: {}
  destinationName: azuremonitor
  signals:
  - TRACES
  - METRICS
  - LOGS
  type: azuremonitor
2

Apply the YAML using kubectl
kubectl apply -f azuremonitor.yaml
⌘I