Monitoring Azure Event Hub Logger
Your API logging stops silently when the Event Hub behind an Azure API Management Service Event Hub Logger goes missing or gets disabled. The Nodinite Azure Monitoring Agent watches every Event Hub Logger in your Azure API Management Services, evaluates its state, and lets the right people act from a role-based Monitor View, without access to the Azure Portal.
- ✅ Detect disruptions and configuration errors in Event Hub Loggers instantly
- ✅ Share role-based Monitor Views and Remote Actions with your teams
- ✅ Search the alert history and get alerts through Alarm Plugins
- ✅ Limit direct Azure access and increase security
Learn how to perform Azure Monitoring of the Azure API Management Service Event Hub Logger. To log API traffic through the Event Hub Logger with a policy, see Azure API Management logging.
Nodinite also provides Monitoring for these Azure API Management Service types:
This page explains how you monitor Azure API Management Service Event Hub Logger options using Nodinite from one or more role-based Monitor Views. You define global or specific thresholds, manage configured Event Hub Loggers, and use Remote Actions to swiftly address reported problems. The Managing Azure API Management Event Hub Logger page details the Remote Actions. The Azure Event Hub page covers monitoring of the target Event Hub itself.
Example list of monitored Azure API Management Services Event Hub Loggers in a Nodinite Monitor View.
How Monitoring Works
The agent evaluates each Event Hub Logger as a Resource, and the Monitoring Service collects the result. Users with access to a Monitor View see the state, act on it with Remote Actions, and receive alerts through Alarm Plugins.
API Management Service"] -->|"Azure REST API"| AG["fa:fa-monitor-waveform Azure Monitoring Agent"] AG --> OK["fa:fa-check OK
Target Event Hub found"] AG --> WA["fa:fa-triangle-exclamation Warning
Resource ID missing or invalid"] AG --> ER["fa:fa-xmark Error
Target Event Hub missing or disabled"] AG --> UN["fa:fa-ban Unavailable
No network or access"] WA --> AP["fa:fa-bell Alarm Plugins"] ER --> AP WA --> RA["fa:fa-bolt Remote Actions
Edit Resource ID"] style OK fill:#93d16d style WA fill:#FFD525 style ER fill:#c33d34,color:#fff style UN fill:#c33d34,color:#fff style AG fill:#2678BD,color:#fff
Diagram: The agent evaluates each Event Hub Logger into OK (green), Warning (yellow), or Error and Unavailable (red); Warning and Error raise alerts, and you fix the Resource ID with the Edit Remote Action.
Monitoring Features
- State Evaluation - Provide state according to user-defined thresholds.
If Nodinite can't check your Azure API Management Service items' state, chances are no one else can use them either.
- Services have Automatic Discovery
- The Nodinite Azure Agent uses the Azure REST API. Hence, the agent manages the Azure API Management Services Event Hub Loggers dynamically.
- Category-based monitoring - The Azure API Management Service Event Hub Logger belongs to the Category API Management Service - Logger
- Share access to individual Event Hub Loggers from within Nodinite using one or more role-based Monitor Views.
- The Application name is constructed as
/ConfigurationName/ResourceGroupName/API Management Service Name/. This naming scheme provides uniqueness, even if you deploy the same set of artifacts/services with the same name in different Monitored Azure Subscriptions.
The Application path combines the configuration, Resource Group, and API Management Service names.
State evaluation for Azure API Management Service Event Hub Logger
The configured Subscriptions with Azure API Management Services Event Hub Loggers to monitor appear within Nodinite as one or more Resources. For example, if you have two Event Hub Loggers, you have two Resources in Nodinite.
- The Nodinite Resources name is the name of the deployed Event Hub Logger.
Each item (presented in Nodinite as a Resource) evaluates with a state (OK, Warning, Error, Unavailable).
You can override the evaluation process by configuring the Expected State option available for all Nodinite Resources. Use Auto Healing when you want Nodinite to act on a state change automatically.
API Management Service Event Hub Logger
For the Category API Management Service - Logger, the state evaluates as described in the table below:
| State | Status | Description | Actions |
|---|---|---|---|
| 🚫 Unavailable | Resource not available |
|
Review Prerequisites |
| ❌ Error |
|
See Target Event Hub does not exist | Edit |
| ⚠️ Warning | Resource ID is missing or is invalid New 6.2.1.2 | See Missing Resource ID | Edit |
| ✅ OK | Within user-defined thresholds | Operational | Edit Details |
Alert history for Azure API Management Service
During root cause analysis or other purposes, it helps to understand how often your Azure API Management Service problems happen. If your Monitor View allows it, you can search for historical state changes for the provided time span, either for all your Azure API Management Services or individually. The generic instructions on how to Add or manage Monitor View and the Resource State History guide detail this topic.
| Search | Resource history |
|---|---|
 Search for alert history for all resources in the Monitor View |
 Alert history for the selected Azure API Management Service item |
Frequently asked questions
Use the Troubleshooting guide to find the FAQ and answers to known problems.
Missing Resource ID
New 6.2.1.2
If you see the following Warning (Configuration error: the Resource ID is missing or has an invalid configuration. Please contact the System Administrator to update this configuration):
Warning message when the Resource ID is missing for an Event Hub Logger.
You must update the configuration to resolve this problem. Earlier versions of this agent lacked the feature to set and update the Resource ID.
As a User with the Remote Actions grant, click the Actions button, then Edit and update the configuration with a valid path to the target Event Hub entity.
/subscriptions/{subscription-id}/resourceGroups/{resource-group}/providers/Microsoft.EventHub/namespaces/{namespace}/eventhubs/{eventhub-name}
Note
The target Event Hub entity might be located in a different resource group or namespace than the API Management Service where this Event Hub logger will be utilized.
Target Event Hub from Resource ID does not exist
New 6.2.1.2
If you see the following Error (Target Event Hub: '{{NAME}}' from Resource ID does not exist. Ensure the configuration is valid and the Resource Group: '{{RESOURCEGROUPNAME}}' with the target Event Hub entity is included in the Monitoring):
Error message when the Target Event Hub is either missing for an Event Hub Logger or the Resource Group is not included in the Monitoring.
The problem exists because the target Event Hub entity is either missing (potentially deleted) or the Resource Group is not included in the Monitoring.
Ensure the target Event Hub entity exists, for example from the Azure Event Hub monitoring Resources.
Ensure the Resource Group with the target Event Hub entity is included in the Monitoring (Configuration).
Review Azure access rights.
Ensure the Resource ID has proper configuration:
/subscriptions/{subscription-id}/resourceGroups/{resource-group}/providers/Microsoft.EventHub/namespaces/{namespace}/eventhubs/{eventhub-name}