You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/api-management/monitor-api-management.md
+3-6Lines changed: 3 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,6 +27,7 @@ This table describes how you can collect data to monitor your service, and what
27
27
28
28
## Built in monitoring for API Management
29
29
30
+
Azure API management has the following built in monitoring features.
30
31
31
32
### Get API analytics in Azure API Management
32
33
@@ -53,7 +54,7 @@ With API analytics, analyze the usage and performance of the APIs in your API Ma
53
54
- Users
54
55
- Requests
55
56
56
-
API analytics provides data on requests, including failed and unauthorized requests. Geography values are , based on IP address mapping. There can be a delay in the availability of analytics data.
57
+
API analytics provides data on requests, including failed and unauthorized requests. Geography values are based on IP address mapping. There can be a delay in the availability of analytics data.
57
58
58
59
#### Azure Monitor-based dashboard
59
60
@@ -491,8 +492,6 @@ Addressing the issue of telemetry data flow from API Management to Application I
491
492
492
493
### Enable logging of developer portal usage in Azure API Management
This article shows you how to enable Azure Monitor logs for auditing and troubleshooting usage of the API Management [developer portal](developer-portal-overview.md). When enabled through a diagnostic setting, the logs collect information about the requests that are received and processed by the developer portal.
497
496
498
497
Developer portal usage logs include data about activity in the developer portal, including:
@@ -515,7 +514,7 @@ To configure a diagnostic setting for developer portal usage logs:
515
514
1.**Diagnostic setting name**: Enter a descriptive name.
516
515
1.**Category groups**: Optionally make a selection for your scenario.
517
516
1. Under **Categories**: Select **Logs related to Developer Portal usage**. Optionally select other categories as needed.
518
-
1. Under **Destination details**, select one or more options and specify details for the destination. For example, archive logs to a storage account or stream them to an event hub. [Learn more](/azure/azure-monitor/essentials/diagnostic-settings).
517
+
1. Under **Destination details**, select one or more options and specify details for the destination. For example, archive logs to a storage account or stream them to an event hub. For more information, see [Diagnostic settings in Azure Monitor](/azure/azure-monitor/essentials/diagnostic-settings).
519
518
1. Select **Save**.
520
519
521
520
#### View diagnostic log data
@@ -532,8 +531,6 @@ If you send logs to a storage account, you can access the data in the Azure port
532
531
533
532
### Integrate Application Insights to developer portal
A popular feature of Azure Monitor is Application Insights. It's an extensible Application Performance Management (APM) service for developers and DevOps professionals. Use it to monitor your developer portal and detect performance anomalies. Application Insights includes powerful analytics tools to help you learn what users actually do while visiting your developer portal.
0 commit comments