Monitoring Event Grid Topics in Azure
Event-driven integrations fail silently when an Event Grid Topic has no Event Subscriptions or a Subscription loses its dead-letter destination: events vanish, and nobody notices until a business process stops. The Nodinite Azure Monitoring Agent watches your Azure Event Grid Topics and Topic Subscriptions, raises alerts on bad configuration, and lets the right people inspect the details from a Monitor View, without access to the Azure Portal.
- ✅ Instant alerts for Event Grid Topic and Topic Subscription configuration problems
- ✅ Dead-lettering watchdog that flags Subscriptions without a dead-letter destination
- ✅ Auto-discovery of Event Grid resources in every configured Azure Subscription
- ✅ Role-based self-service through Monitor Views, with Remote Actions for details
- ✅ 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 Grid 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 Grid page describes the available Remote Actions in detail.
Example: List of monitored Event Grid resources in a Nodinite Monitor View.
How Monitoring Works
The Azure Monitoring Agent discovers your Event Grid Topics and Topic Subscriptions 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.
and Topic Subscriptions"] -->|"Azure REST API"| AG["fa:fa-monitor-waveform Azure Monitoring Agent"] AG --> OK["fa:fa-check OK
Operational"] AG --> WA["fa:fa-triangle-exclamation Warning
No Event Subscriptions or
no dead-letter destination"] AG --> UN["fa:fa-ban Unavailable
Network or security problem"] WA -->|"State change"| AP["fa:fa-bell Alarm Plugins"] UN -->|"State change"| AP OK --> RA["fa:fa-circle-info Details
Remote Action"] style OK fill:#93d16d style WA fill:#FFD525 style UN fill:#c33d34,color:#fff style AG fill:#2678BD,color:#fff style RA fill:#2678BD,color:#fff
Diagram: The agent evaluates each Event Grid resource into OK (green), Warning (yellow), or Unavailable (red); state changes to Warning or Unavailable raise alerts, and the Details Remote Action (blue) shows the configuration.
Monitoring Features
- State Evaluation – Nodinite evaluates state according to a pre-defined policy.
If Nodinite can't check your Event Grid items' state, chances are no one else can use them either.
- Automatic Discovery – Nodinite automatically monitors Event Grids for configured Subscriptions 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.
State evaluation for Event Grid
Nodinite presents each Event Grid Topic to monitor as a Resource. For example, if you have three Event Grid Topics, Nodinite displays three resources.
- The Resources name matches the deployed Event Grid Topic or Event Grid Topic Subscription.
- Monitored Event Grid Topics belong to either:
- The Application name uses the pattern:
Configuration name/Resource Group Name
Example: Event Grid Topic and Subscription categories in Nodinite.
Many other Azure-related Categories exist—see the Azure Logging and Monitoring Overview. The Monitoring Subscription and Monitoring Resource Group pages show how Nodinite also guards the Azure scope that holds your Event Grid resources.
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.
Event Grid Topic
For Event Grid Topic Resources, Nodinite evaluates state as follows:
| State | Status | Description | Actions |
|---|---|---|---|
| 🚫 Unavailable | Resource not available | Nodinite cannot evaluate the 'Event Grid Topic' due to network or security issues | Review prerequisites and the firewall settings |
| ❌ Error | Error threshold breached | N/A | - |
| ⚠️ Warning | Warning threshold breached | Bad configuration – Not operational. No Event Subscriptions configured for this Event Grid Topic | - |
| ✅ OK | Within user-defined thresholds | Operational | Details |
Event Grid Topic Subscription
For Event Grid Topic Subscription Resources, Nodinite evaluates state as follows:
| State | Status | Description | Actions |
|---|---|---|---|
| 🚫 Unavailable | Resource not available | Nodinite cannot evaluate the 'Event Grid Topic Subscription' due to network or security issues | Review prerequisites and the firewall settings |
| ❌ Error | Error threshold breached | N/A | - |
| ⚠️ Warning | Warning threshold breached | Bad configuration – No Dead letter destination set for this subscription. Either the DEAD-LETTERING destination was removed or never set. | - |
| ✅ OK | Within user-defined thresholds | Operational | Details |
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 Grid
Nodinite enables you to analyze alert history for Event Grid resources. When you troubleshoot, you can search for historical state changes for any time span—either for all Event Grid Topics 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 Grid Topic item |
Frequently asked questions
Use the Troubleshooting guide to find answers to common questions and known issues.