Skip to content

Commit a4ead18

Browse files
author
gitName
committed
edits
1 parent 887a585 commit a4ead18

File tree

6 files changed

+13
-58
lines changed

6 files changed

+13
-58
lines changed

articles/api-management/TOC.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -637,8 +637,6 @@
637637
href: self-hosted-gateway-settings-reference.md
638638
- name: Self-hosted gateway Azure Arc configuration
639639
href: self-hosted-gateway-arc-reference.md
640-
- name: Diagnostic logs settings
641-
href: diagnostic-logs-reference.md
642640
- name: Resources
643641
items:
644642
- name: FAQ

articles/api-management/api-management-howto-use-azure-monitor.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: dlepow
77
ms.service: azure-api-management
88
ms.custom: engagement-fy23, devdivchpfy22
99
ms.topic: tutorial
10-
ms.date: 02/24/2025
10+
ms.date: 02/28/2025
1111
ms.author: danlep
1212
---
1313
# Tutorial: Monitor published APIs
@@ -132,7 +132,7 @@ Resource logs (Azure Monitor logs) provide rich information about API Management
132132
> [!NOTE]
133133
> The Consumption tier doesn't support the collection of resource logs.
134134
135-
[!INCLUDE [api-management-diagnostic-settigs](../../includes/api-management-diagnostic-settings.md)]
135+
[!INCLUDE [api-management-diagnostic-settings](../../includes/api-management-diagnostic-settings.md)]
136136
137137
## View logs and metrics in Azure Log Analytics
138138

articles/api-management/diagnostic-logs-reference.md

Lines changed: 0 additions & 49 deletions
This file was deleted.

includes/api-management-api-logging.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,9 +6,9 @@ ms.date: 02/24/2025
66
ms.author: danlep
77
---
88

9-
When you create a diagnostic setting to enable collection of gateway or LLM resource logs, logging is enabled with default settings, which do not include details of request or responses such as response bodies. You can adjust the logging settings for all APIs, or override them for individual APIs. For example, adjust the sampling rate or the verbosity of the gateway log data, enable logging of LLM request or response messages, or disable logging for some APIs.
9+
When you use the portal to create a diagnostic setting to enable collection of API Management gateway or gateway LLM logs, logging is enabled with default settings. Default settings do not include details of requests or responses such as request or response bodies. You can adjust the logging settings for all APIs, or override them for individual APIs. For example, adjust the sampling rate or the verbosity of the gateway log data, enable logging of LLM request or response messages, or disable logging for some APIs.
1010

11-
For details about the logging settings, see [Diagnostic logging settings reference](../articles/api-management/diagnostic-logs-reference.md).
11+
For details about the logging settings, see the [Diagnostic - Create or Update](/rest/api/apimanagement/diagnostic/create-or-update) and the [API diagnostic - Create or Update](/rest/api/apimanagement/api-diagnostic/create-or-update) REST API reference pages.
1212

1313
To configure logging settings for all APIs:
1414

includes/api-management-log-entry-size-limit.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,11 @@
22
author: dlepow
33
ms.service: azure-api-management
44
ms.topic: include
5-
ms.date: 05/15/2024
5+
ms.date: 02/28/2025
66
ms.author: danlep
77
---
88

99
> [!IMPORTANT]
10-
> * If enabled in API Management Gateway logs, logged request or response payloads can be up to 8,192 bytes. API Management also enforces a 32 KB limit for a diagnostic log entry sent to Azure Monitor, which includes the payloads and other attributes such as status codes, headers, and timestamps. If the combined size of the attributes exceeds 32 KB, API Management trims the entry by removing all body and trace content.
11-
> * If enabled in LLM Gateway logs, request or response messages are logged up to 32 KB; messages larger than 32 KB are split and logged in 32 KB chunks including sequence numbers for later reconstruction. Request messages and response messages cannot exceed 2 MB each.
10+
> API Management enforces a 32 KB limit for the size of log entries sent to Azure Monitor. The behavior when the logged data exceeds the limit depends on the log category and the data attributes that are logged:
11+
> * **API Management Gateway logs** - Logged request or response payloads in a log entry, if collected, can be up to 8,192 bytes each. If the combined size of the logged attributes exceeds 32 KB, API Management trims the entry by removing all body and trace content.
12+
> * **LLM Gateway logs** - Request or response messages, if collected, are logged up to 32 KB; messages larger than 32 KB are split and logged in 32 KB chunks including sequence numbers for later reconstruction. Request messages and response messages can't exceed 2 MB each.

redirects/.openpublishing.redirection.api-management.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,10 @@
11
{
22
"redirections": [
3+
{
4+
"source_path_from_root": "/articles/api-management/diagnostic-logs-reference.md",
5+
"redirect_url": "/rest/api/apimanagement/diagnostic/create-or-update",
6+
"redirect_document_id": false
7+
},
38
{
49
"source_path_from_root": "/articles/api-management/gateway-log-schema-reference.md",
510
"redirect_url": "/azure/api-management/monitor-api-management-reference",

0 commit comments

Comments
 (0)