- 5 minutes to read

Manage Azure API Management Service Event Hub Logger monitoring

Take full control of your Azure API Management Service Event Hub Logger monitoring with Nodinite. This guide helps you manage, configure, and troubleshoot all Event Hub Logger monitoring options efficiently, without direct Azure Portal access. You and your teams perform Remote Actions, accelerate root cause analysis, and securely delegate management with role-based self-service.

✅ Perform Remote Actions and manage monitoring for all Event Hub Logger resources
✅ Empower business and IT users with secure, role-based self-service
✅ Reduce risk by limiting direct Azure Portal access
✅ Accelerate root cause analysis with actionable insights

This page describes managing the Event Hub Logger. The API Logging user guide details logging to Nodinite using a Policy, and the Event Hub policy page shows how a policy uses the logger.

Start with Monitoring Azure API Management Service Event Hub Logger to understand the monitored states and threshold context before you edit or delete an Event Hub Logger below. The Monitoring Azure API Management Service page covers the parent service.

To manage other parts of Azure API Management Services using Nodinite, review the following user guides:

Delegate the power to control all or individual Event Hub Loggers to selected team members and the business. This feature enables support and maintenance teams to manage problems with your Event Hub Logger, without granting individual direct access to the Microsoft Azure Portal. By reducing access, you limit attack vectors and minimize the risk of disruption to mission-critical services.

Application Management Team	IT Operations	Business
Let your AM team have the power to detect application-related problems without involving the IT operations team	Stay in complete control with access to everything	Give your business Data and self-service for solutions built using Azure API Management Service

Management Features

To create a new Event Hub Logger, review the Create Event Hub Logger user guide.

For Resources in the Role-based Monitor Views with the Remote Actions privilege grant, the following Remote Actions grouped by Category are available:

Category	Monitoring	Actions	Metrics/Statistics
Event Hub Logger	✅ Yes	Edit Details Delete	-

As an Administrator with access to the Configuration for Monitoring Agents, the additional Monitoring options are available:

Monitoring	Remote Configuration
Monitoring Azure API Management Service Logger	Add and Remove Azure API Management Service connections Enable and Disable Monitoring as specified Edit monitoring thresholds

Event Hub Logger

The 'API Management Service - Logger' Category provides one resource for each Event Hub Logger discovered from configured Azure API Management Services. The name of the Resource is the same as in Azure.

%Name%

Example from a Monitor View with a list of configured 'API Management Service Event Hub Loggers'.

See Monitoring Azure API Management Service for additional details about Azure API Management Service Monitoring.

The API Management Service - Logger category provides Resources that display the evaluated monitored state according to user-defined thresholds.

The following Remote Actions are available for the API Management Service - Logger Category.

Here's an example with a list of Remote Actions as seen from the dropdown menu of the Actions button.

Details

To view the selected Event Hub Logger, click the Action button and then click the Details menu item within the 'Control Center' section.

Use the 'Details' action menu item to open the details modal for the selected Event Hub Logger.

Next, click the option to present the modal.

Here's an example of details for the selected Event Hub Logger.

Edit

To manage the Event Hub Logger, click the Action button and then click the Edit menu item within the 'Control Center' section.

Here's an example of the Edit Action button menu item.

Next, click the option to present the modal.

Here's an example of the modal where you manage the Event Hub Logger.

Event Hub Name - The name of the Event Hub Logger (to be used in your API Logging Policy)
Credential Connection String - The connection string for the destination Event Hub:

Example: Endpoint=sb://namespacename.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=gurumeditation=;EntityPath=nameoftargeteventhubentity
Resource ID ^{New 6.2.1.2} - Enter the path to the target Event Hub entity:

Format: /subscriptions/{subscription-id}/resourceGroups/{resource-group}/providers/Microsoft.EventHub/namespaces/{namespace}/eventhubs/{eventhub-name}
Example: subscriptions/abc123538-3e2b-4490-9feb-7dfe30a6683c/resourceGroups/Default-Storage-NorthEurope/providers/Microsoft.EventHub/namespaces/Contoso/eventhubs/apimlogger

Note
This configuration is manual and can be tricky to set up correctly, especially since 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. The Missing Resource ID FAQ explains the Warning you get when the Resource ID is wrong, and Azure Event Hub monitoring shows the target Event Hub.