Skip to main content
Sumo Logic

Collect Logs for the Azure Audit App from Event Hub

To collect Azure Activity logs from Event Hub, you configure an HTTP source on a hosted collector, use an Azure Resource Manager (ARM) template to create necessary Azure resources, define required environment variables, create an blob container for failover data, and export Activity Logs to Event Hub.

This page has instructions for configuring a pipeline for shipping Azure Audit logs from Azure Monitor to an Event Hub, on to an Azure Function, and finally to an HTTP source on a hosted collector in Sumo Logic.

Here’s how the solution fits together:

  • Azure Monitor collects logs for most Microsoft Azure services, including Azure Audit, and streams the data to an Azure Event Hub. 
  • Azure Event Hubs is a data streaming platform and event ingestion service. In this pipeline, an Event Hub streams the logs collected by Azure Monitor to an Azure function. 
  • The Azure function is a small piece of code that is triggered by Event Hub to send logs to the Sumo HTTP Source, function logs to one Storage Account, and and failover data to another.

CollectLogsforAzureAudit.png

Step 1. Configure an HTTP source

In this step, you configure an HTTP source to which the Azure function will send Azure Activity logs.

  1. Select a hosted collector where you want to configure the HTTP source. If desired, create a new hosted collector, as described on Configure a Hosted Collector.
  2. Configure an HTTP source, as described on HTTP Logs and Metrics Source

Step 2. Configure Azure resources using ARM template

To deploy a Sumo provided ARM template, follow the instructions in Step 2 for Collecting logs from Azure monitor.

Step 3. Export Activity Logs to Event Hub

  1. In the search bar, search, and select Activity Log.

    ActivityLog.png
  2. In the Activity log window, click Diagnostic Settings.
    DiagonosticSetting.png
  3. In the Diagnostic Settings window, click Add Diagnostic settings.
    AddDiagonosticSetting.png

  4. Select the log type in Category details that you want to ingest.

    • Select the Stream to an event hub checkbox and then select the following:

      • Subscription. Pull-down, select a subscription.

      • Event Hub Namespace. Pull-down, select the SumoAzureLogsNamespace<UniqueSuffix> namespace created by the ARM template in Step 2.

      • Event Hub name (optional). Select “insights-operational-logs”.

      • Event hub policy name. Leave the default policy, RootManageSharedAccessKey, or select another as desired.

    • Click Save.

LogtypeDiagonosticSetting.png

Troubleshooting

If logs are not flowing into Sumo Logic, see Troubleshooting