build validationn

Author: gitName

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

@@ -132,27 +132,7 @@ Resource logs (Azure Monitor logs) provide rich information about API Management
 > [!NOTE]
 > The Consumption tier doesn't support the collection of resource logs.
 
-To configure resource logs:
-
-1. In the [Azure portal](https://portal.azure.com), navigate to your API Management instance.
-2. Select **Monitoring** > **Diagnostic settings**.
-
-    :::image type="content" source="media/api-management-howto-use-azure-monitor/api-management-diagnostic-logs-blade.png" alt-text="Screenshot of Diagnostic settings item in Monitoring menu in the portal.":::
-
-1. Select **+ Add diagnostic setting**.
-1. Select the logs or metrics that you want to collect.
-
-   You have several options about where to send the logs and metrics. For example, archive resource logs along with metrics to a storage account, stream them to an event hub, or send them to a Log Analytics workspace.
-
-   > [!TIP]
-   > If you select a Log Analytics workspace, you can choose to store the data in the resource-specific ApiManagementGatewayLogs table or store in the general AzureDiagnostics table. We recommend using the resource-specific table for log destinations that support it. [Learn more](/azure/azure-monitor/essentials/resource-logs#send-to-log-analytics-workspace)
-
-1. After configuring details for the log destination or destinations, select **Save**. 
-
-> [!NOTE]
-> Adding a diagnostic setting object might result in a failure if the [MinApiVersion property](/dotnet/api/microsoft.azure.management.apimanagement.models.apiversionconstraint.minapiversion) of your API Management service is set to any API version higher than 2022-09-01-preview. 
-
-For more information, see [Create diagnostic settings to send platform logs and metrics to different destinations](/azure/azure-monitor/essentials/diagnostic-settings).
+[!INCLUDE [api-management-diagonstic-settigs](../../includes/api-management-diagonstic-settings.md)]
  
 ## View logs and metrics in Azure Log Analytics
 

includes/api-management-api-logging.md

@@ -8,7 +8,7 @@ ms.author: danlep
 
 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.
 
-For details about the logging settings, see [Diagnostic logging settings reference](diagnostic-logs-reference.md).
+For details about the logging settings, see [Diagnostic logging settings reference](../articles/api-management/diagnostic-logs-reference.md).
 
 To configure logging settings for all APIs:
 

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

@@ -7,4 +7,5 @@ ms.author: danlep
 ---
 
 > [!IMPORTANT]
-> If enabled in 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. 
+> * 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. 
+> * 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.