Stream Azure monitoring data to an event hub or external partner
Azure Monitor provides full stack monitoring for applications and services in Azure, in other clouds, and on-premises. In most cases, the most effective method to stream monitoring data to external tools is using Azure Event Hubs. This article provides a brief description on how to stream data and then lists some of the partners where you can send it. Some have special integration with Azure Monitor and may be hosted on Azure.
Create an Event Hubs namespace
Before you configure streaming for any data source, you need to create an Event Hubs namespace and event hub. This namespace and event hub is the destination for all of your monitoring data. An Event Hubs namespace is a logical grouping of event hubs that share the same access policy, much like a storage account has individual blobs within that storage account. Consider the following details about the event hubs namespace and event hubs that you use for streaming monitoring data:
- The number of throughput units allows you to increase throughput scale for your event hubs. Only one throughput unit is typically necessary. If you need to scale up as your log usage increases, you can manually increase the number of throughput units for the namespace or enable auto inflation.
- The number of partitions allows you to parallelize consumption across many consumers. A single partition can support up to 20 MBps or approximately 20,000 messages per second. Depending on the tool consuming the data, it may or may not support consuming from multiple partitions. Four partitions are reasonable to start with if you're not sure about the number of partitions to set.
- You set message retention on your event hub to at least seven days. If your consuming tool goes down for more than a day, this retention ensures that the tool can pick up where it left off for events up to seven days old.
- You should use the default consumer group for your event hub. There's no need to create other consumer groups or use a separate consumer group unless you plan to have two different tools consume the same data from the same event hub.
- For the Azure Activity log, you pick an Event Hubs namespace, and Azure Monitor creates an event hub within that namespace called insights-logs-operational-logs. For other log types, you can either choose an existing event hub or have Azure Monitor create an event hub per log category.
- Outbound port 5671 and 5672 must typically be opened on the computer or VNET consuming data from the event hub.
Monitoring data available
Sources of monitoring data for Azure Monitor describes the data tiers for Azure applications and the kinds of data available for each. The following table lists each of these tiers and a description of how that data can be streamed to an event hub. Follow the links provided for further detail.
|Azure tenant||Azure Active Directory audit logs||Configure a tenant diagnostic setting on your Azure AD tenant. See Tutorial: Stream Azure Active Directory logs to an Azure event hub for details.|
|Azure subscription||Azure Activity Log||Create a log profile to export Activity Log events to Event Hubs. See Stream Azure platform logs to Azure Event Hubs for details.|
|Azure resources||Platform metrics
|Both types of data are sent to an event hub using a resource diagnostic setting. See Stream Azure resource logs to an event hub for details.|
|Operating system (guest)||Azure virtual machines||Install the Azure Diagnostics Extension on Windows and Linux virtual machines in Azure. See Streaming Azure Diagnostics data in the hot path by using Event Hubs for details on Windows VMs and Use Linux Diagnostic Extension to monitor metrics and logs for details on Linux VMs.|
|Application code||Application Insights||Use diagnostic settings to stream to event hubs. This is only available with workspace-based Application Insights resources. For help setting up workspace-based Application Insights resources, see Workspace-based Application Insights resources and Migrate to workspace-based Application Insights resources.|
Manual streaming with Logic App
For data that you can't directly stream to an event hub, you can write to Azure storage and then use a time-triggered Logic App that pulls data from blob storage and pushes it as a message to the event hub.
Partner tools with Azure Monitor integration
Routing your monitoring data to an event hub with Azure Monitor enables you to easily integrate with external SIEM and monitoring tools. Examples of tools with Azure Monitor integration include the following:
|Tool||Hosted in Azure||Description|
|IBM QRadar||No||The Microsoft Azure DSM and Microsoft Azure Event Hub Protocol are available for download from the IBM support website.|
|Splunk||No||Splunk Add-on for Microsoft Cloud Services is an open source project available in Splunkbase.
If you can't install an add-on in your Splunk instance, if for example you're using a proxy or running on Splunk Cloud, you can forward these events to the Splunk HTTP Event Collector using Azure Function For Splunk, which is triggered by new messages in the event hub.
|SumoLogic||No||Instructions for setting up SumoLogic to consume data from an event hub are available at Collect Logs for the Azure Audit App from Event Hub.|
|ArcSight||No||The ArcSight Azure Event Hub smart connector is available as part of the ArcSight smart connector collection.|
|Syslog server||No||If you want to stream Azure Monitor data directly to a syslog server, you can use a solution based on an Azure function.|
|LogRhythm||No||Instructions to set up LogRhythm to collect logs from an event hub are available here.|
|Logz.io||Yes||For more information, see Getting started with monitoring and logging using Logz.io for Java apps running on Azure|
Other partners may also be available. For a more complete list of all Azure Monitor partners and their capabilities, see Azure Monitor partner integrations.
Submit and view feedback for