Manage Azure Event Hub Monitoring
Take control of your Azure Event Hub monitoring with Nodinite. This guide shows how you empower your teams to securely manage, monitor, and take action on Event Hubs and Event Hub Namespaces—without direct Azure Portal access.
- ✅ Proactively monitor Event Hubs and Namespaces for issues
- ✅ Enable secure, role-based self-service for business and support teams
- ✅ Access actionable details and Remote Actions (Details, Edit, Post) from a single interface
- ✅ Tune Flow Monitoring thresholds per Event Hub without opening Azure New 7.8.0
- ✅ Keep every action in the Nodinite Audit Log
Nodinite enables you to delegate management and insights for selected Event Hubs in Azure. Your support and maintenance teams gain deep insights for root cause analysis—while you minimize risk by limiting direct Azure Portal access. This approach reduces potential attack vectors and safeguards mission-critical services from accidental disruption.
Start with Monitoring Event Hub if you want the monitored Event Hub scope and Flow Monitoring threshold context before you use the Details, Edit, or Post actions below.
Flow Monitoring adds inactivity detection for Event Hub entities. Nodinite triggers an alert when the Azure Agent does not detect activity for the configured threshold. New 7.8.0
Diagram: The Azure Monitoring Agent (blue) monitors and manages Azure Event Hub Namespaces and the Event Hubs inside them (teal).
| Application Management Team | IT Operations | Business |
|---|---|---|
| Your AM team can proactively manage Event Hubs without disrupting IT operations | You maintain full control and visibility over all actions | Your business receives actionable insights and self-service for solutions built on Event Hub |
Example: Nodinite Monitor View with Event Hub resources.
Management Features
For Resources in Role-based Monitor Views with Remote Actions privileges, your Users can use the following actions, grouped by Category:
Example of Event Hub categories in Nodinite.
| Category | Monitoring | Actions | Metrics/Statistics |
|---|---|---|---|
| Event Hub | - | - | |
| Event Hub - Namespace | - | - |
Info
The Nodinite Audit Log records every Remote Action that you and other Users perform.
As an Administrator with access to Configuration for Monitoring Agents, you can:
| Monitoring | Remote Configuration |
|---|---|
| Monitoring Event Hub |
|
Flow Monitoring Configuration
Flow Monitoring detects inactivity for Event Hub entities and raises alerts when no activity is detected within the configured threshold. The Flow Monitoring Threshold Model explains how Nodinite picks the threshold and evaluates the state.
Use Remote Configuration to define a global default for all Event Hub entities. On the Event Hubs tab, open General, check Enable data flow monitoring, and set the Flow warning TimeSpan.
Example of the global Flow Monitoring threshold (Flow warning TimeSpan) on the General tab in Remote Configuration.
If required, override the global default for a named Event Hub on the Specific Event Hub Monitoring tab: add an entry with the Namespace, the Event Hub name, and its own Flow warning TimeSpan. Nodinite doesn't monitor an Event Hub that an Exclude Filter also matches, and an entry that no longer matches an Event Hub in Azure makes the resource Unavailable.
Example of a Specific Event Hub Monitoring entry that overrides the global threshold for one Event Hub.
You can also set the override directly from a Monitor View by using the Edit Remote Action on the Event Hub resource.
Tip
Flow Monitoring watches one Event Hub. To track message volumes and expected activity across the systems on both sides of the Event Hub, use Non-Events Monitoring.
Event Hub
The 'Event Hub' Category provides one Resource for each Event Hub found, with the Event Hub name as the Resource name.
Example: Monitor View with a list of 'Event Hubs'.
See Monitoring Event Hub for additional details about Event Hub Monitoring.
The Event Hub category provides Resources that display the evaluated monitored state according to built-in rules.
You can perform the following Remote Actions for the Event Hub Category:
Example of available remote actions for Event Hub resources, including Details, Edit, and Post.
Event Hub Details
To view details about the selected Event Hub Resource, click the Action button and select Details from the 'Control Center' menu.
Use the 'Details' action to open the details modal for the selected Event Hub.
Next, select the option to present the modal.
Example of the updated Event Hub Details modal including Flow Monitoring configuration data.
Edit Flow Monitoring Override
To configure a specific Flow Monitoring threshold for the selected Event Hub Resource, click the Action button and select Edit from the 'Control Center' menu.
Example of the Edit modal where you configure a specific Flow Monitoring override for an Event Hub resource.
Post
To post to the Event Hub Resource, click the Action button and select Post from the 'Control Center' menu.
Use the 'Post' action to open the modal for the selected Event Hub.
Next, select the option to present the modal.
Example of the Post modal for sending a message to the selected Event Hub.
Note
A posted message counts as Event Hub ingress, which Azure may bill depending on your tier. The Azure Costs for Blob Storage and Event Hub page explains the Event Hub meters.
Unavailable Resource Due to Missing Access or Invalid Configuration
An Event Hub resource can become Unavailable if the entity is removed in Azure, is no longer accessible, or if a specific Flow Monitoring configuration is invalid. Check the App Registration rights in the Prerequisites and the firewall settings when the agent can't reach the Event Hub.
Example of an unavailable Event Hub resource caused by missing Azure access, deleted entities, or invalid specific configuration.
Event Hub Namespace
The 'Event Hub - Namespace' Category provides one Resource for each Event Hub Namespace found, with the Namespace name as the Resource name.
Example: Monitor View with a list of 'Event Hub Namespaces'.
See Monitoring Event Hub for additional details about Event Hub Monitoring.
The Event Hub - Namespace category provides Resources that display the evaluated monitored state according to built-in rules.
You can perform the following Remote Actions for the Event Hub - Namespace Category:
Example of available remote actions for Event Hub Namespace resources.
Event Hub Namespace Details
To view details about the selected Event Hub Namespace Resource, click the Action button and select Details from the 'Control Center' menu.
Use the 'Details' action to open the details modal for the selected Event Hub Namespace.
Next, select the option to present the modal.
Example of details shown for the selected Event Hub Namespace resource.
Next Steps
Related Topics
- Azure Logging and Monitoring Overview
- Prerequisites for Azure Agent
- Firewall settings for the Azure agent
- Troubleshooting
- Managing Event Grid
- Managing the APIM Event Hub Logger
- Configure Event Hubs for Azure Logic Apps
- Azure Costs for Blob Storage and Event Hub
- Non-Events Monitoring
- Remote Actions
- Roles
- Audit Log