Monitoring Event Hubs in Azure

When an Event Hub is disabled, stops accepting send operations, or simply stops receiving events, every downstream integration that depends on it goes quiet. The Nodinite Azure Monitoring Agent gives you full visibility and control over your Azure Event Hubs and Event Hub Namespaces: it evaluates their state, detects stopped data flow, and alerts the right people—without direct Azure Portal access.

• ✅ Instant alerts for Event Hub and Event Hub Namespace issues
• ✅ State Evaluation that catches disabled Event Hubs and blocked send operations
• ✅ Flow Monitoring that detects missing Event Hub activity with global and specific thresholds ^{New 7.8.0}
• ✅ Role-based self-service with actionable details and Remote Actions from a single interface
• ✅ Alerts outside Nodinite through Alarm Plugins, for example email or an HTTP webhook

Nodinite empowers your integration and support teams to detect, analyze, and resolve issues quickly. You securely share access to Event Hub resources using role-based Monitor Views, so Users see only what they need. This approach streamlines troubleshooting, reduces risk, and keeps your business running smoothly. The Managing Event Hub page describes the available Remote Actions in detail.

Example: List of monitored Event Hub resources in a Nodinite Monitor View.

How Monitoring Works

The Azure Monitoring Agent discovers the Event Hubs in your configured Namespaces with the Azure REST API, evaluates each one as a Resource, and reports the result to the Nodinite Monitoring Service. Users with access to a Monitor View see the state in the Web Client, and Alarm Plugins push state changes to the people on duty.

Diagram: The agent evaluates each Event Hub into OK (green), Warning (yellow), or Error and Unavailable (red); state changes raise alerts, and you investigate and tune thresholds with Remote Actions (blue).

Monitoring Features

• State Evaluation – Nodinite evaluates state according to a 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. You add Subscriptions in the agent Configuration.
• Category-based monitoring – Nodinite groups monitored Resources by Categories.
• Role-based access – You 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 adds inactivity detection: it 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.

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.

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
• The Application name uses the pattern: Configuration name/Resource Group Name

Example: Event Hub and Namespace categories in Nodinite.

Many other Azure-related Categories exist—see the Azure Logging and Monitoring Overview.

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:

Event Hub Namespace

For Event Hub Namespace Resources, Nodinite evaluates state as follows:

If the agent can't reach Azure at all, check that the App Registration has the rights listed in Azure user rights and services and the Azure Application Access guide.

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

Event Hubs used by other Nodinite agents

Several Nodinite logging options use an Event Hub as intermediate storage, so the Event Hubs you monitor here often carry your own logging traffic:

• The Azure Logic Apps agent reads the Logic Apps diagnostic stream from an Event Hub; see Configure Event Hubs for Azure Logic Apps.
• Azure API Management logs through an Event Hub Logger, which the Azure Monitoring Agent also monitors.
• The Azure Costs for Blob Storage and Event Hub page explains what an Event Hub adds to your Azure bill and how to lower it.

Frequently asked questions

Use the Troubleshooting guide to find answers to common questions and known issues.

Next Steps

• Manage Event Hub
• Configure Flow Monitoring
• Configure the Azure Monitoring Agent

Related Topics

• Azure Monitoring Agent
• Azure Logging and Monitoring Overview
• Prerequisites
• Firewall settings for the Azure agent
• Monitoring Event Grid
• Monitoring the APIM Event Hub Logger
• Configure Event Hubs for Azure Logic Apps
• Azure Costs for Blob Storage and Event Hub
• Azure Service Bus Monitoring
• Non-Events Monitoring
• Resources
• Categories
• Applications
• Alarm Plugins
• Troubleshooting