Enable monitoring of Azure API Management Service APIs with Nodinite

- 3 minutes to read

:fa-clou# ds: Monitoring Azure Management Service APIs

Learn how to monitor APIs using the Nodinite the Azure Monitoring Agent.

graph LR subgraph "Nodinite" roMonitor[fal:fa-monitor-waveform Nodinite Azure Monitoring] end subgraph "Azure Cloud" roMonitor --> roapimgmtServices(fal:fa-clouds API Management Service) roapimgmtServices --- roAPI(fal:fa-cloud-upload API) roapimgmtServices --- roAPICert(fal:fa-file-certificate Certificate) roapimgmtServices --- roAPILogger(fal:fa-arrow-to-bottom Event Hub Logger) roapimgmtServices --- roAPIMNW(fal:fa-chart-network Private Endpoint) end

Nodinite also has Monitoring for these other Azure API Management Service types:

This page provides documentation about Azure API Management Service API Monitoring options using Nodinite from one or more role-based Monitor Views. Nodinite monitors the state of content in Azure API Management Service APIs, as specified by user-defined thresholds, either global or specific. You can manage configured Azure API Management Services APIs; Remote commands are available as Actions to help you swiftly address reported problems. The Remote Actions are detailed on the Managing Azure API Management Service APIs page.

Example list of monitored Azure API Management Services APIs 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 APIs are dynamically managed.
Category-based monitoring - The Azure API Management Service API belongs to the Category API Management Service - API
Share access to individual APIs 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 APIs

The configured Subscriptions with Azure API Management Services APIs 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 Azure API Management Service.

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 feature available for all Nodinite Resources.

API Management Service API

For the API Management Service - API Resource, the state evaluates as described in the table below:

State	Status	Description	Actions
Unavailable	Resource not available	Evaluation of the 'API Management Service' is not possible either due to network or security-related problems	Review prerequisites
Error	Error threshold is breached	N/A
Warning	Warning threshold is breached	One or more problems exists API is not current
OK	Within user-defined thresholds	Operational	Test API 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.