edits

dlepow · dlepow · commit d516a82951ab · 2024-05-15T13:52:10.000-07:00
diff --git a/articles/api-management/api-management-howto-use-azure-monitor.md b/articles/api-management/api-management-howto-use-azure-monitor.md
@@ -179,7 +179,7 @@ For more information about using resource logs for API Management, see:
 
 ## Modify API logging settings
 
-By default, when you create a diagnostic setting to enable collection of resource logs, logging is enabled for all APIs, with default settings. 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 data, or disable logging for some APIs.
+By default, when you create a diagnostic setting to enable collection of resource logs, logging is enabled for all APIs, with default settings. 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 data, enable logging of headers or request or response payloads, or disable logging for some APIs.
 
 For details about the logging settings, see [Diagnostic logging settings reference](diagnostic-logs-reference.md).
 
@@ -188,16 +188,17 @@ To configure logging settings for all APIs:
 1. In the left menu of your API Management instance, select **APIs** > **All APIs**.
 1. Select the **Settings** tab from the top bar.
 1. Scroll down to the **Diagnostic Logs** section, and select the **Azure Monitor** tab.
-1. Review the settings and make changes if needed. For example, adjust the sampling rate or verbosity of the logs, or enable logging of headers or request or response payloads. Select **Save**. 
+1. Review the settings and make changes if needed. Select **Save**. 
 
 To configure logging settings for a specific API:
 
 1. In the left menu of your API Management instance, select **APIs** and then the name of the API.
 1. Select the **Settings** tab from the top bar.
 1. Scroll down to the **Diagnostic Logs** section, and select the **Azure Monitor** tab.
-1. Review the settings and make changes if needed. For example, adjust the sampling rate or verbosity of the logs, or enable logging of headers or request or response payloads. Select **Save**. 
+1. Review the settings and make changes if needed. Select **Save**. 
 
-[!INCLUDE [api-management-log-entry-size-limit](../../includes/api-management-log-entry-size-limit.md)]
+> [!IMPORTANT]
+> [!INCLUDE [api-management-log-entry-size-limit](../../includes/api-management-log-entry-size-limit.md)]
 
 ## Next steps
 
diff --git a/articles/api-management/diagnostic-logs-reference.md b/articles/api-management/diagnostic-logs-reference.md
@@ -35,11 +35,13 @@ This reference describes settings for API diagnostics logging from an API Manage
 | 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  | 
 | 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).  |
 | Headers to log              | list                              | Specifies the headers that are logged for requests and responses.  Default: no headers are logged.                                                                                                                                                                                                             |
-| Number of payload (body) bytes to log | integer                           | Specifies the number of initial bytes of the frontend request or response body or backend request or response body that are logged. Maximum: 8,192. Default: 0<br/><br/>   [!INCLUDE [api-management-log-entry-size-limit](../../includes/api-management-log-entry-size-limit.md)]                                                                                                                                                                                                |
+| 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                                                                                                                                                                                                |
 | 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.                                                                                                                                                                        |
 | 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.                                                                                                                                                                   |
 | 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.                                                                                                                                                                        |
-| 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.                                                     
+| 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.     
+
+<sup>*</sup><br/><br/>[!INCLUDE [api-management-log-entry-size-limit](../../includes/api-management-log-entry-size-limit.md)]                                                
 
 ## Next steps
 
diff --git a/includes/api-management-log-entry-size-limit.md b/includes/api-management-log-entry-size-limit.md
@@ -5,5 +5,5 @@ ms.topic: include
 ms.date: 05/15/2024
 ms.author: danlep
 ---
-> [!IMPORTANT]
-> When logging large request or response payloads, consider both the payload (body) size limit and API Management's log entry limit of 32 KB. The API Management log entry includes other attributes such as status codes, headers, URLs, and timestamps. If a log entry could exceed the limit, API Management trims it by removing all body and trace content. An entry that still exceeds the limit is dropped. 
+
+When logging large request or response payloads, consider both the payload (body) size limit and API Management's log entry limit of 32 KB. The API Management log entry includes other attributes such as status codes, headers, URLs, and timestamps. If a log entry could exceed the limit, API Management trims it by removing all body and trace content before sending to Azure Monitor. An entry that still exceeds the limit is dropped. 
