Skip to content

Commit ab54a27

Browse files
committed
edit
1 parent 8b6e8cb commit ab54a27

File tree

3 files changed

+5
-5
lines changed

3 files changed

+5
-5
lines changed

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

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -197,8 +197,7 @@ To configure logging settings for a specific API:
197197
1. Scroll down to the **Diagnostic Logs** section, and select the **Azure Monitor** tab.
198198
1. Review the settings and make changes if needed. Select **Save**.
199199
200-
> [!IMPORTANT]
201-
> [!INCLUDE [api-management-log-entry-size-limit](../../includes/api-management-log-entry-size-limit.md)]
200+
[!INCLUDE [api-management-log-entry-size-limit](../../includes/api-management-log-entry-size-limit.md)]
202201
203202
## Next steps
204203

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -35,13 +35,13 @@ This reference describes settings for API diagnostics logging from an API Manage
3535
| Verbosity | | Specifies the verbosity of the logs and whether custom traces that are configured in [trace](trace-policy.md) policies are logged. <br/><br/>* Error - failed requests, and custom traces of severity `error`<br/>* Information - failed and successful requests, and custom traces of severity `error` and `information`<br/> * Verbose - failed and successful requests, and custom traces of severity `error`, `information`, and `verbose`<br/><br/>Default: Information |
3636
| Correlation protocol | | Specifies the protocol used to correlate telemetry sent by multiple components to Application Insights. Default: Legacy <br/><br/>For information, see [Telemetry correlation in Application Insights](../azure-monitor/app/distributed-tracing-telemetry-correlation.md). |
3737
| Headers to log | list | Specifies the headers that are logged for requests and responses. Default: no headers are logged. |
38-
| Number of payload (body) bytes to log<sup>*</sup>| integer | Specifies the number of initial bytes of the frontend or backend request or response body that are logged. Maximum: 8,192. Default: 0 |
38+
| Number of payload (body) bytes to log| integer | Specifies the number of initial bytes of the frontend or backend request or response body that are logged. Maximum: 8,192. Default: 0 |
3939
| Frontend Request | | Specifies whether and how *frontend requests* (requests incoming to the API Management gateway) are logged.<br/><br/> If this setting is enabled, specify **Headers to log**, **Number of payload bytes to log**, or both. |
4040
| Frontend Response | | Specifies whether and how *frontend responses* (responses outgoing from the API Management gateway) are logged.<br/><br/> If this setting is enabled, specify **Headers to log**, **Number of payload bytes to log**, or both. |
4141
| Backend Request | | Specifies whether and how *backend requests* (requests outgoing from the API Management gateway) are logged.<br/><br/> If this setting is enabled, specify **Headers to log**, **Number of payload bytes to log**, or both. |
4242
| Backend Response | | Specifies whether and how *backend responses* (responses incoming to the API Management gateway) are logged. <br/><br/> If this setting is enabled, specify **Headers to log**, **Number of payload bytes to log**, or both.
4343

44-
<sup>*</sup><br/><br/>[!INCLUDE [api-management-log-entry-size-limit](../../includes/api-management-log-entry-size-limit.md)]
44+
[!INCLUDE [api-management-log-entry-size-limit](../../includes/api-management-log-entry-size-limit.md)]
4545

4646
## Next steps
4747

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

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,4 +6,5 @@ ms.date: 05/15/2024
66
ms.author: danlep
77
---
88

9-
If enabled, logged request or response payloads can be up to 8,192 bytes. API Management also has a 32 KB limit for the size of a diagnostic log entry sent to Azure Monitor. The diagnostic log entry includes the request or response payloads and other attributes such as status codes, headers, URLs, and timestamps. If the size of the combined attributes exceeds 32 KB, API Management trims the log entry to 32 KB by removing all body and trace content. An entry that still exceeds the limit is dropped.
9+
> [!IMPORTANT]
10+
> If enabled, 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 to 32 KB by removing all body and trace content. An entry that still exceeds the limit is dropped.

0 commit comments

Comments
 (0)