Monitoring Event Hubs in Azure
Learn how to perform Monitoring of Azure Event Hub and Namespaces.
This page provides documentation about Event Hub and Event Hub Namespace Monitoring options using Nodinite from one or more role-based Monitor Views. Nodinite monitors the configured Event Hubs and Namespaces. Monitoring is based in pre-defined thresholds; Remote commands are available as Actions to help you swiftly address reported problems. The Remote Actions are detailed on the Managing Event Hub page.
Example list of monitored Event Hub resources in a Nodinite Monitor View.
Monitoring Features
- State Evaluation - Provide state evaluation according to pre-defined policy.
If Nodinite can't check your Event Hub items' state, chances are no one else can use them either.
- Event Hubs for configured Namespaces are automatically monitored.
- The Nodinite Azure Agent makes use of the Azure Rest API. Hence, Event Hubs presents automatically.
- Category-based monitoring - The monitored Resources groups by the Nodinite concept of Categories.
- Share access to individual items from within Nodinite using one or more role-based Monitor Views.
State evaluation for Event Hub
The Event Hubs to monitor manifests within Nodinite as one or more Resources. For example, if you have three Event Hubs, you will have three Resources in Nodinite.
- The Nodinite Resources name is the same as the deployed Event Hub name and Event Hub Namespaces.
- Monitored Event Hubs belong to either of the following:
Many other Azure related Categories exists as well, please review the Azure Logging and Monitoring Overview
- The Application name is created with the following pattern:
Configuration name/Resource Group Name
Each item (presented in Nodinite as a Resource) evaluates with a state (i.e. OK, Warning, Error, Unavailable).
You can override the evaluation process by configuring the Expected State option available for all Nodinite Resources.
Event Hub
For Event Hub Resources, the state evaluates as described in the table below:
| State | Status | Description | Actions | |
|---|---|---|---|---|
| Unavailable | Resource not available | Evaluation of the 'Event Hub' is not possible either due to network or security-related problems | Review prerequisites | |
| Error | Error threshold is breached | Event Hub is Disabled | - | |
| Warning | Warning threshold is breached | Not operational. The Event Hub does not allow send operations | - | |
| OK | Within user-defined thresholds | Operational | Details Post |
Event Hub Namespace
For Event Hub Namespace Resources, the state evaluates as described in the table below:
| State | Status | Description | Actions | |
|---|---|---|---|---|
| Unavailable | Resource not available | Evaluation of the 'Event Hub Namespace' is not possible either due to network or security-related problems | Review prerequisites | |
| Error | Error threshold is breached | N/A | - | |
| Warning | Warning threshold is breached | N/A | - | |
| OK | Within user-defined thresholds | Operational | Details |
Alert history for Event Hub
During root cause analysis or other purposes, it might be helpful to understand how often your Event Hub problems happen. If your Monitor View allows it, you can search for historical state changes for the provided time-span either for all your Event Hub or individually. This topic is further detailed within the generic instructions on how to Add or manage Monitor View page.
| Search | Resource history |
|---|---|
 Search for alert history for all resources in the Monitor View |
 Alert history for the selected Event Hub item |
Frequently asked questions
Use the troubleshooting guide to find the FAQ and answers to known problems.