Skip to main content

Overview

Bronto supports several methods for ingesting data from Azure environments. The right choice depends on where your telemetry originates, whether you need trace data, your infrastructure preferences, and cost constraints. Bronto ingests OpenTelemetry logs and traces (metrics are not yet supported). Broadly, Azure telemetry falls into two categories:
  • Platform, diagnostic, and activity logs — emitted by Azure services through diagnostic settings. These are streamed to Bronto via the Azure Event Hub Forwarder.
  • Application logs and traces — emitted by your own workloads. Send these to Bronto using OpenTelemetry on Azure — a self-managed Collector or the OpenTelemetry SDK.

Service-to-Method Mapping

Different Azure services suit different ingestion methods. The recommended method is the simplest path that gets the data into Bronto; alternatives may be preferable depending on your existing infrastructure or cost constraints. Each service name in the table below links to a per-source landing page with a short summary of what the service emits and the configuration entry points for that data.
Where the OpenTelemetry SDK supports your runtime, prefer OTel-based instrumentation — it sends logs and traces through one pipeline and gives you consistent service.name / service.namespace routing. OpenTelemetry on Azure covers a self-managed Collector (recommended) and direct SDK export for AKS, Container Apps, Container Instances, VMs, App Service, and Functions.
Azure ServiceRecommended MethodAlternatives
Azure Virtual Machines / VM Scale SetsOTel CollectorAzure Monitor Distro, Event Hub Forwarder (diagnostic logs)
Azure Kubernetes Service (AKS)OTel CollectorAzure Monitor Distro, Event Hub Forwarder (control plane / diagnostic logs)
Azure Container AppsOTel Collector (Collector container) / OTel SDKEvent Hub Forwarder (diagnostic logs)
Azure Container Instances (ACI)OTel Collector (sidecar)
Azure App ServiceOTel SDKAzure Monitor Distro, Event Hub Forwarder (diagnostic logs)
Azure FunctionsOTel SDKAzure Monitor Distro, Event Hub Forwarder (Function App logs)
Azure SQL DatabaseEvent Hub Forwarder (diagnostic / audit logs)
Azure Monitor / Activity LogsEvent Hub Forwarder
Microsoft Entra ID (sign-in / audit logs)Event Hub Forwarder
Network Security Perimeter LogsEvent Hub Forwarder

Ingestion Methods

Bronto supports the following Azure ingestion methods:
  • Azure Event Hub Forwarder — A Bronto Function App subscribes to an Event Hub and forwards platform, diagnostic, and activity logs streamed to it via diagnostic settings. It can also receive logs re-exported from a Log Analytics workspace via Data Export.
  • OpenTelemetry on Azure — Application logs and traces via a self-managed OpenTelemetry Collector (recommended) or the OpenTelemetry SDK.
  • Azure Monitor OpenTelemetry Distro — Microsoft’s SDK distro; a convenient option for teams already using Application Insights who want to forward the same data to Bronto.

For assistance or questions, contact support@bronto.io.