Monitoring Azure API Management Service
After you install the Instana host agent, the Azure API Management Service sensor is automatically installed. You can view metrics that are related to the Azure API Management Service in the Instana UI after you configure Azure API Management sensor as outlined in the Configuring Azure API Management sensor section.
For more information about the other supported Azure services, see the Azure documentation.
Supported information
Supported operating systems
The supported operating systems of the Azure API Management Service sensor are consistent with host agents requirements. For more information, see the supported operating systems for host agents.
Configuring Azure API Management sensor
By default, the Azure API Management sensor is enabled. You can disable the sensor and filter by tags and resource groups by using the agent configuration file <agentinstall_dir>/etc/instana/configuration.yaml
. See the following
example:
com.instana.plugin.azure.apimanagement:
# Valid values: true, false
enabled: false # enabled (true) by default
# Comma separated list of tags in key:value format
include_tags:
# Comma separated list of tags in key:value format
exclude_tags:
# Comma separated list of resource groups
include_resource_groups:
# Comma separated list of resource groups
exclude_resource_groups:
You can disable the Azure API Management sensor. To stop monitoring Azure API Management services, use the following configuration:
com.instana.plugin.azure.apimanagement:
enabled: false
You can define multiple tags and resource groups, which are separated by a comma. Provide tags as key-value pairs separated by :
. To simplify the configuration, you can specify the tags and resource groups that you want to include
or exclude from discovery. If a tag or resource group appears in both the include and exclude lists, the exclude list takes priority. If you don't need to filter services, you don't need to configure it. It is not mandatory to define all values
to enable filtering.
To include services by tags in the discovery, use the following configuration:
com.instana.plugin.azure.apimanagement:
include_tags: # Comma separated list of tags in key:value format (e.g. env:prod,env:staging)
To exclude services by tags from discovery use following configuration:
com.instana.plugin.azure.apimanagement:
exclude_tags: # Comma separated list of tags in key:value format (e.g. env:dev,env:test)
To include services by resource groups into discovery use following configuration:
com.instana.plugin.azure.apimanagement:
include_resource_groups: # Comma separated list of resource groups (e.g. rg_prod,rg_staging)
To exclude services by resource groups from discovery use following configuration:
com.instana.plugin.azure.apimanagement:
exclude_resource_groups: # Comma separated list of resource groups (e.g. rg_dev,rg_test)
You can configure discovery filtering globally for all Azure services. If you set a filter for the Azure API Management service, it overrides the global filters. For more information about global Azure service discovery filtering, see the Azure Configuration.
Viewing metrics
To view the metrics, complete the following steps:
- In the Instana UI sidebar, select Infrastructure.
- Click a specific monitored host to view its dashboard, which displays all collected metrics and monitored processes.
Metrics are pulled every minute, which is the resolution Azure provides for monitoring of these services.
Configuration data
API Management Service details | Description |
---|---|
Name | The name of the API Management service |
Resource Group | The resource group of the API Management service |
Location | The region where the API Management instance is located |
Subscription ID | The subscription ID of the API Management service |
Publisher Name | Publisher name |
Provisioning State | API Management service provisioning state |
Gateway URL | Gateway URL of the API Management service |
Portal URL | Publisher portal endpoint URL of the API Management service |
SKU | SKU (Pricing tier) of the API Management |
Service metrics
Service metric | Description |
---|---|
Capacity | |
Capacity | Utilization metric for API Management service |
Gateway Requests | |
Total Requests | Number of gateway requests |
Successful Requests | Number of successful gateway requests |
Unauthorized Requests | Number of unauthorized gateway requests |
Failed Requests | Number of failures in gateway requests |
Other Requests | Number of other gateway requests |
Duration (Latency) | Overall duration of gateway requests in milliseconds |
Event Hub Events | |
Successful Events | Number of successful Event Hub events |
TotalFailed Events | Number of failed Event Hub events |
Rejected Events | Number of rejected Event Hub events (wrong configuration or unauthorized) |
Throttled Events | Number of throttled Event Hub events |
Timedout Events | Number of timed out Event Hub events |
Dropped Events | Number of events skipped because of queue size limit reached |
Total Bytes Sent | Total size of Event Hub events in bytes |
API and operation metric
Metric | Description |
---|---|
Bandwidth | |
Bandwidth | Bandwidth consumed |
Call Count | |
Blocked Calls | Number of calls blocked due to invalid credentials. This includes calls returning HttpStatusCode.Unauthorize and HttpStatusCode.Forbidden and HttpStatusCode.TooManyRequests |
Failed Calls | Number of calls failed due to proxy or backend errors. This includes calls returning HttpStatusCode.BadRequest(400) and any Code between HttpStatusCode.InternalServerError (500) and 600 |
Other Calls | Number of other calls |
Successful Calls | Number of successful calls. This includes calls returning HttpStatusCode <= 301 and HttpStatusCode.NotModified and HttpStatusCode.TemporaryRedirect |
Total Calls | Total number of calls |
Cache Hits/Misses | |
Cache Hits | Number of times when content was served from cache policy |
Cache Misses | Number of times content was fetched from backend |
API Response Time | |
Average API Response Time | Average time that it took to process a request |
Maximum API Response Time | Maximum time that it took to process a request |
Minimum API Response Time | Minimum time that it took to process a request |
Service Response Time | |
Average Service Response Time | Average time that it took to process a request on the backend |
Maximum Service Response Time | Maximum time that it took to process a request on the backend |
Minimum Service Response Time | Minimum time that it took to process a request on the backend |
Health signatures
Each sensor has a curated knowledgebase of health signatures that are continuously evaluated against incoming metrics. These signatures are used to raise issues or incidents based on user impact.
Built-in events trigger issues or incidents based on failing health signatures on entities, and custom events trigger issues or incidents based on the thresholds of an individual metric of any given entity.
For information about built-events for Azure API Management Service, see the Built-in events reference.