Monitoring Event Hubs in Azure
Gain full visibility and control over your Azure Event Hubs and Namespaces with Nodinite. This page shows you how to monitor Event Hub resources, receive proactive alerts, and take action—without ever needing direct Azure Portal access.
- ✅ Get instant alerts for Event Hub and Namespace issues
- ✅ Monitor and manage thresholds for Event Hub resources
- ✅ Access actionable details and Remote Actions from a single interface
- ✅ Detect missing Event Hub activity using Flow Monitoring thresholdsNew 7.8.0
Nodinite empowers your integration and support teams to detect, analyze, and resolve issues quickly. You can securely share access to Event Hub resources using role-based Monitor Views. This approach streamlines troubleshooting, reduces risk, and keeps your business running smoothly.
Example: List of monitored Event Hub resources in a Nodinite Monitor View.
Monitoring Features
- State Evaluation – Nodinite evaluates state according to pre-defined policy.
If Nodinite can't check your Event Hub items' state, chances are no one else can use them either.
- Automatic Discovery – Nodinite automatically monitors Event Hubs for configured Namespaces using the Azure Agent and Azure REST API.
- Category-based monitoring – Nodinite groups monitored Resources by Categories.
- Role-based access – You can share access to individual items using one or more Role-based Monitor Views.
- Flow Monitoring – Nodinite triggers an alert if the Azure Agent does not detect activity on an Event Hub within the configured threshold.
Flow Monitoring Threshold Model
New 7.8.0 Flow Monitoring lets you detect inactive Event Hub entities before downstream integrations fail.
The Azure Agent evaluates each monitored Event Hub against one Flow warning TimeSpan:
- Global Data Flow Monitoring – the default TimeSpan from Remote Configuration applies to every Event Hub without a specific setting.
- Specific Data Flow Monitoring – a TimeSpan set for one named Event Hub (namespace and name) overrides the global default for that Event Hub.
When the Azure Agent detects no incoming events within the applicable TimeSpan, Nodinite evaluates the Event Hub Resource as Warning. The Log Text states how long the Event Hub has been inactive, for example No incoming events in the last 15 hours 5 minutes 59 seconds, data flow appears to have stopped.
Example: Two Event Hubs in Warning because no events arrived within their Global and Specific Flow Monitoring thresholds, and one Unavailable Event Hub whose Specific Data Flow Monitoring entry no longer exists in Azure.
The Details Remote Action shows whether the Global or a Specific threshold applies to the selected Event Hub, the time span, and whether Flow Monitoring is enabled. See Event Hub Details.
To set the Global default or a Specific override, see Flow Monitoring Configuration and the Edit Remote Action on the Managing Event Hub page.
State evaluation for Event Hub
Nodinite presents each Event Hub to monitor as a Resource. For example, if you have three Event Hubs, Nodinite displays three resources.
- The Resources name matches the deployed Event Hub or Event Hub Namespace.
- Monitored Event Hubs belong to either:
- Event Hub Category
- Event Hub Namespace Category
Example: Event Hub and Namespace categories in Nodinite.
Many other Azure-related Categories exist—see the Azure Logging and Monitoring Overview.
- The Application name uses the pattern:
Configuration name/Resource Group Name
Each item (presented as a Resource) evaluates with a state (OK, Warning, Error, Unavailable).
You can override the evaluation process by configuring the Expected State option for any Nodinite Resource.
If an Event Hub entity is removed, becomes inaccessible, or has an invalid specific Flow Monitoring configuration, Nodinite can evaluate the resource as Unavailable.
Example of an unavailable resource caused by missing Azure entities, access issues, or invalid specific Flow Monitoring settings.
Event Hub
For Event Hub Resources, Nodinite evaluates state as follows:
| State | Status | Description | Actions |
|---|---|---|---|
| 🚫 Unavailable | Resource not available | Nodinite cannot evaluate the 'Event Hub' due to network or security issues, or an Event Hub configured for Specific Data Flow Monitoring was not found in Azure | Review prerequisites |
| ❌ Error | Error threshold breached | Event Hub is Disabled | - |
| ⚠️ Warning | Warning threshold breached | Not operational. The Event Hub does not allow send operations, or no incoming events arrived within the Flow Monitoring threshold | - |
| ✅ OK | Within user-defined thresholds | Operational | Details Edit Post |
Event Hub Namespace
For Event Hub Namespace Resources, Nodinite evaluates state as follows:
| State | Status | Description | Actions |
|---|---|---|---|
| 🚫 Unavailable | Resource not available | Nodinite cannot evaluate the 'Event Hub Namespace' due to network or security issues | Review prerequisites |
| ❌ Error | Error threshold breached | N/A | - |
| ⚠️ Warning | Warning threshold breached | N/A | - |
| ✅ OK | Within user-defined thresholds | Operational | Details |
Alert history for Event Hub
Nodinite enables you to analyze alert history for Event Hub resources. When you troubleshoot, you can search for historical state changes for any time span—either for all Event Hubs or for individual resources. See the Add or manage Monitor View page for more details.
| 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 answers to common questions and known issues.