Azure Event Hubs metrics in Azure Monitor

Event Hubs metrics give you the state of Event Hubs resources in your Azure subscription. With a rich set of metrics data, you can assess the overall health of your event hubs not only at the namespace level, but also at the entity level. These statistics can be important as they help you to monitor the state of your event hubs. Metrics can also help troubleshoot root-cause issues without needing to contact Azure support.

Azure Monitor provides unified user interfaces for monitoring across various Azure services. For more information, see Monitoring in Microsoft Azure and the Retrieve Azure Monitor metrics with .NET sample on GitHub.

Access metrics

Azure Monitor provides multiple ways to access metrics. You can either access metrics through the Azure portal, or use the Azure Monitor APIs (REST and .NET) and analysis solutions such as Log Analytics and Event Hubs. For more information, see Monitoring data collected by Azure Monitor.

Metrics are enabled by default, and you can access the most recent 30 days of data. If you need to keep data for a longer period of time, you can archive metrics data to an Azure Storage account. This setting can be configured in diagnostic settings in Azure Monitor.

Access metrics in the portal

You can monitor metrics over time in the Azure portal. The following example shows how to view successful requests and incoming requests at the account level:

View successful metrics

You can also access metrics directly via the namespace. To do so, select your namespace and then select Metrics. To display metrics filtered to the scope of the event hub, select the event hub and then select Metrics.

For metrics supporting dimensions, you must filter with the desired dimension value as shown in the following example:

Filter with dimension value

Billing

Using metrics in Azure Monitor is currently free. However, if you use other solutions that ingest metrics data, you may be billed by these solutions. For example, you are billed by Azure Storage if you archive metrics data to an Azure Storage account. You are also billed by Azure if you stream metrics data to Azure Monitor logs for advanced analysis.

The following metrics give you an overview of the health of your service.

Note

We are deprecating several metrics as they are moved under a different name. This might require you to update your references. Metrics marked with the "deprecated" keyword will not be supported going forward.

All metrics values are sent to Azure Monitor every minute. The time granularity defines the time interval for which metrics values are presented. The supported time interval for all Event Hubs metrics is 1 minute.

Azure Event Hubs metrics

For a list of metrics supported by the service, see Azure Event Hubs

Note

When a user error occurs, Azure Event Hubs updates the User Errors metric, but doesn't log any other diagnostic information. Therefore, you need to capture details on user errors in your applications. Or, you can also convert the telemetry generated when messages are sent or received into application insights. For an example, see Tracking with Application Insights.

Azure Monitor integration with SIEM tools

Routing your monitoring data (activity logs, diagnostics logs, and so on.) to an event hub with Azure Monitor enables you to easily integrate with Security Information and Event Management (SIEM) tools. For more information, see the following articles/blog posts:

In the scenario where an SIEM tool consumes log data from an event hub, if you see no incoming messages or you see incoming messages but no outgoing messages in the metrics graph, follow these steps:

  • If there are no incoming messages, it means that the Azure Monitor service isn't moving audit/diagnostics logs into the event hub. Open a support ticket with the Azure Monitor team in this scenario.
  • if there are incoming messages, but no outgoing messages, it means that the SIEM application isn't reading the messages. Contact the SIEM provider to determine whether the configuration of the event hub those applications is correct.

Next steps

For more information about Event Hubs, visit the following links: