Skip to main content
Use OpenTelemetry to collect telemetry from your Azure workloads including App Services, Function Apps, Service Bus, Cosmos DB, and other Azure services. This data answers questions like:
  • Which App Services are experiencing the highest latency?
  • How are my Function Apps performing across different regions?
  • What is the error rate for my Service Bus queues?
  • Are there any performance bottlenecks in my Cosmos DB operations?
Adding telemetry to Azure and then analyzing with Honeycomb provides a flexible way to aggregate, structure, and enrich events from applications running on Azure. This data answers questions like:
  • How did response time change after deploying to a new App Service plan?
  • How does application performance vary across Azure regions?
  • Are application errors happening in specific services, or across the entire environment?

​
Getting Started

Honeycomb supports Azure through OpenTelemetry Collectors configured with Azure-specific receivers:
  • AzureMonitorReceiver for collecting metrics from Azure services
  • AzureEventHubReceiver for collecting logs from Azure Event Hub
This setup allows you to send telemetry from App Services, Function Apps, Service Bus, Cosmos DB, and other Azure workloads to Honeycomb.

​
Before You Begin

Before you begin, you should have:
  • An Azure subscription with the services you want to monitor
  • Access to configure Azure Monitor and Event Hub
  • A Honeycomb Ingest API Key You’ll need a Honeycomb Ingest API Key with the Can create services/datasets permission. This key lets your application send telemetry to Honeycomb and create a dataset for your service.
    When deploying to production, replace this key with a separate key that does not allow dataset creation. This helps protect your data structure in live environments.

​
Getting Help

To ask questions and learn more, join our Pollinators Community Slack.