Monitoring Azure Event Hub Logger
Learn how to perform Azure Monitoring of the Azure API Management Service Event Hub Logger.
Nodinite also has Monitoring for these other Azure API Management Service types:
This page provides documentation about Azure API Management Service Event Hub Logger Monitoring options using Nodinite from one or more role-based Monitor Views. Nodinite monitors the state of Azure API Management Service Event Hub Loggers, as specified by system-defined thresholds, either global or specific. You can manage configured Azure API Management Services Event Hub Loggers; Remote commands are available as Actions to help you swiftly address reported problems. The Remote Actions are detailed on the Managing Azure API Management Event Hub Logger page.
Example list of monitored Azure API Management Services Event Hub Loggers in a Nodinite Monitor View.
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 makes use of the Azure Rest API. Hence, the Azure API Management Services Event Hub Loggers are dynamically managed.
- 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.
State evaluation for Azure API Management Service Event Hub Logger
The configured Subscriptions with Azure API Management Services Event Hub Loggers to monitor manifests within Nodinite as one or more Resources. For example, if you have two Services, you will 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 (i.e. OK, Warning, Error, Unavailable).
You can override the evaluation process by configuring the Expected State option available for all Nodinite Resources.
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 |
|
|||
| Warning | Resource ID is missing or is invalid New 6.2.1.2 | |||
| OK | Within user-defined thresholds | Operational | Edit Details |
Alert history for Azure API Management Service
During root cause analysis or other purposes, it might be helpful 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 Service or individually. This topic is further detailed within the generic instructions on how to Add or manage Monitor View page.
| 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 was missing 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 '{{NAME}}'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 exist 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 exist.
Ensure the Resource Group with the target Event Hub entity is included in the Monitoring.
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}