Manage Azure Event Hub Monitoring
Take control of your Azure Event Hub monitoring with Nodinite. This guide shows you how to empower your teams to securely manage, monitor, and take action on Event Hubs and 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 from a single interface
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.
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: High-level overview of how Nodinite monitors and manages Azure Event Hubs.
| 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, you can:
Example of Event Hub categories in Nodinite.
| Category | Monitoring | Actions | Metrics/Statistics |
|---|---|---|---|
| Event Hub | - | - | |
| Event Hub - Namespace | - | - |
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.
Use Remote Configuration to define a global default for all Event Hub entities.
Example of the global Flow Monitoring threshold settings in Remote Configuration.
If required, you can override the global default for a specific Event Hub by using the Edit remote action on that resource.
Example of a specific Flow Monitoring override for an individual Event Hub resource.
Event Hub
The 'Event Hub' Category provides one Resource for each Event Hub found 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.
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.
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 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 Step
- Monitoring Event Hub
- Configuring the Nodinite Azure Monitoring agent