- 7 minutes to read

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

An Event Hub Namespace and its Event Hubs, an Event Hub's Action menu, Details and the Edit modal with Monitor Data Flow Settings, animated walkthrough (7.12)
Animated walkthrough: the Namespace and its Event Hubs in a Monitor View, an Event Hub's Action menu with Details, Edit, and Post, its Details, and Edit with the Monitor Data Flow Settings. The walkthrough closes the modal without Save.

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

graph LR subgraph NOD["Nodinite Azure Event Hub Monitoring"] roA["fa:fa-monitor-waveform Azure Monitoring Agent"] --- roM("fa:fa-watch-fitness Monitoring") end subgraph AZ["Azure"] roNS("fa:fa-box-alt Event Hub Namespace") roNS --- roEH("fa:fa-border-outer Event Hub") end roM --- roNS style roA fill:#2678BD,color:#fff style roM fill:#2678BD,color:#fff style roNS fill:#3F827B,color:#fff style roEH fill:#3F827B,color:#fff

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

Event Hub Resources in a Monitor View filtered on the Event Hub Category, one in Warning (7.12)
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:

The Event Hub and Event Hub - Namespace Categories in the Category filter (7.12)
Example of Event Hub categories in Nodinite.

Category Monitoring Actions Metrics/Statistics
Event Hub ✅ Yes -
Event Hub - Namespace - -

The Event Hub Resource itself changes state: Flow Monitoring turns it Warning when no events arrive in time, and an Event Hub that Azure no longer lets the agent use turns Warning or Unavailable. See Monitoring Event Hub for the rules.

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
  • Add and remove Subscriptions
  • Enable and disable monitoring as specified
  • Manage exclusion filters
  • Set global Flow Monitoring threshold defaults

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 Monitoring tab, open the Subscription, then Event Hubs > General, check Enable data flow monitoring, and set the Flow warning TimeSpan.

The Event Hubs General tab in Remote Configuration with Enable monitoring of Event Hub and Enable data flow monitoring (7.12)
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: click Add under Specific Event Hubs and enter the Namespace, the Event Hub name, and its own Flow warning TimeSpan. As the tab itself says, an Exclude Filter wins: Nodinite drops an Event Hub that an Exclude Filter also matches. A wrong Namespace is reported as a warning that names the correct one, and an unknown Event Hub name is ignored.

The Specific Event Hub Monitoring tab in Remote Configuration with the Add button (7.12)
Example of the Specific Event Hub Monitoring tab, where each entry 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.

Event Hub Resources in a Monitor View, filtered on the Namespace (7.12)
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:

Remote Actions menu for an Event Hub Resource with Details, Edit, and Post under Control Center (7.12)
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.

Details Remote Action in the Control Center menu (7.12)
Use the 'Details' action to open the details modal for the selected Event Hub.

Next, select the option to present the modal.

Event Hub Details modal with the Data flow monitoring fields and the Consumer Groups (7.12)
Example of the Event Hub Details modal. Data flow monitoring shows whether the global or a specific setting applies, with its Data flow monitoring time span and Data flow monitoring status; Consumer Groups lists each group with its Metadata.

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.

Event Hub Edit modal with the Event Hub details and the Monitor Data Flow Settings section (7.12)
Example of the Edit modal for an Event Hub.

The Edit modal shows the Event Hub's details (Namespace, Provisioning state, Partition count, Message retention, Created, and Updated), followed by the Monitor Data Flow Settings section:

  • Enable data flow monitoring for this Event Hub - Overrides the global Event Hub flow window for this Event Hub
  • Flow warning TimeSpan - How long the Event Hub may go without new events before the agent warns, as hh:mm:ss (�0:10:00 is 10 minutes) or d.hh:mm:ss for longer windows (1.02:30:00 is 1 day, 2 hours, and 30 minutes)

Click Save to store the setting in the agent's configuration.

Post

To post to the Event Hub Resource, click the Action button and select Post from the 'Control Center' menu.

Post Remote Action in the Control Center menu (7.12)
Use the 'Post' action to open the modal for the selected Event Hub.

Next, select the option to present the modal.

Event Hub Post modal with the Body field and the Post button (7.12)
Example of the Post modal: type the message in Body and click Post to send it 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 or is no longer accessible. An Event Hub whose status in Azure stops it from receiving events, such as SendDisabled, turns Warning. Check the App Registration rights in the Prerequisites and the firewall settings when the agent can't reach the Event Hub.

An Event Hub Resource in Warning because send operations are disabled (7.12)
Example of an Event Hub in Warning: "The Event Hub may not function properly because send operations …". The Namespace Details show its status as SendDisabled.

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.

Event Hub Namespace Resources in a Monitor View filtered on the Event Hub - Namespace Category (7.12)
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:

Remote Actions menu for an Event Hub Namespace Resource with Details under Control Center (7.12)
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.

Event Hub Namespace Details Remote Action in the Control Center menu (7.12)
Use the 'Details' action to open the details modal for the selected Event Hub Namespace.

Next, select the option to present the modal.

Event Hub Namespace Details modal with the Event Hub Entities list (7.12)
Example of the Namespace Details modal. Event Hub Entities lists each Event Hub with its Status, Message retention, and Partition count.

Next Steps