Verified the article, reviewed the content, and fixed all editorial issues. Updated ms.date w.r.t freshness pass.

Author: Akhilesh-microsoft

articles/container-apps/log-options.md

@@ -6,7 +6,7 @@ author: craigshoemaker
 ms.service: azure-container-apps
 ms.custom: devx-track-azurecli
 ms.topic: conceptual
-ms.date: 09/29/2022
+ms.date: 12/05/2024
 ms.author: cshoe
 ---
 
@@ -22,12 +22,12 @@ Container Apps application logs consist of two different categories:
 
 You can choose between these logs destinations:
 
-- **Log Analytics**: Azure Monitor Log Analytics is the default storage and viewing option.  Your logs are stored in a Log Analytics workspace where they can be viewed and analyzed using Log Analytics queries.  To learn more about Log Analytics, see [Azure Monitor Log Analytics](log-monitoring.md).
+- **Log Analytics**: Azure Monitor Log Analytics is the default storage and viewing option. Your logs are stored in a Log Analytics workspace where they can be viewed and analyzed using Log Analytics queries. To learn more about Log Analytics, see [Azure Monitor Log Analytics](log-monitoring.md).
 - **Azure Monitor**: Azure Monitor routes logs to one or more destinations:
     - Log Analytics workspace for viewing and analysis.
     - Azure storage account to archive.
     - Azure event hub for data ingestion and analytic services. For more information, see [Azure Event Hubs](../event-hubs/event-hubs-about.md).
-    - An Azure partner monitoring solution such as Datadog, Elastic, Logz.io and others.  For more information, see [Partner solutions](../partner-solutions/overview.md).  
+    - An Azure partner monitoring solution such as Datadog, Elastic, Logz.io, and others. For more information, see [Partner solutions](../partner-solutions/overview.md). 
 - **Don't save logs**: You can disable the storage of log data. When disabled, you can still view real-time container logs via the **Logs stream** feature in your container app. For more information, see [Log streaming](log-streaming.md).
 
 When *Don't save logs* or the *Azure Monitor* destination is selected, the **Logs** menu item providing the Log Analytics query editor in the Azure portal is disabled.
@@ -39,47 +39,47 @@ Use these steps to configure the logging options for your Container Apps environ
 1. Go to the **Logging Options** on your Container Apps environment window in the portal.
     :::image type="content" source="media/observability/log-opts-screenshot-log-analytics.png" alt-text="Screenshot of logs destinations.":::
 1. You can choose from the following **Logs Destination** options:
-    - **Log Analytics**: With this option, you select a Log Analytics workspace to store your log data.  Your logs can be viewed through Log Analytics queries.  To learn more about Log Analytics, see [Azure Monitor Log Analytics](log-monitoring.md).
+    - **Log Analytics**: With this option, you select a Log Analytics workspace to store your log data. Your logs can be viewed through Log Analytics queries. To learn more about Log Analytics, see [Azure Monitor Log Analytics](log-monitoring.md).
     - **Azure Monitor**: Azure Monitor routes your logs to a destination. When you select this option, you must select **Diagnostic settings** to complete the configuration after you select **Save** on this page.
-    - **Don't save logs**:  This option disables the storage of log data.
+    - **Don't save logs**: This option disables the storage of log data.
 1. Select **Save**.
     :::image type="content" source="media/observability/log-opts-screenshot-page-save-button.png" alt-text="Screenshot Logging options page.":::
-1. If you have selected **Azure Monitor** as your logs destination, you must configure **Diagnostic settings**.  The **Diagnostic settings** item appears below the **Logging options** menu item.
+1. If you selected **Azure Monitor** as your logs destination, you must configure **Diagnostic settings**. The **Diagnostic settings** item appears below the **Logging options** menu item.
 
 ### Diagnostic settings
 
 When you select **Azure Monitor** as your logs destination, you must configure the destination details. Select **Diagnostic settings** from the left side menu of the Container Apps Environment window in the portal. You might need to refresh the page for **Diagnostic settings** to appear.
 
 :::image type="content" source="media/observability/log-opts-diag-setting-menu-item.png" alt-text="Screenshot Diagnostic setting menu item.":::
 
-Destination details are saved as *diagnostic settings*.  You can create up to five diagnostic settings for your container app environment. You can configure different log categories for each diagnostic setting. For example, create one diagnostic setting to send the system logs category to one destination, and another to send the container console logs category to another destination.
+Destination details are saved as *diagnostic settings*. You can create up to five diagnostic settings for your container app environment. You can configure different log categories for each diagnostic setting. For example, create one diagnostic setting to send the system logs category to one destination, and another to send the container console logs category to another destination.
 
 To create a new *diagnostic setting*:
 
 1. Select **Add diagnostic setting**.
     :::image type="content" source="media/observability/diag-setting-new-diag-setting.png" alt-text="Screenshot Diagnostic setting Add new diagnostic setting.":::
 1. Enter a name for your diagnostic setting.
     :::image type="content" source="media/observability/diag-setting-dialog.png" alt-text="Screenshot Diagnostics settings dialog.":::
-1. Select the log **Category groups** or **Categories** you want to send to this destination.  You can select one or more categories.  
+1. Select the log **Category groups** or **Categories** you want to send to this destination. You can select one or more categories. 
 
 1. Select one or more **Destination details**:
-    - **Send to Log Analytics workspace**:  Select from existing Log Analytics workspaces.
+    - **Send to Log Analytics workspace**: Select from existing Log Analytics workspaces.
     :::image type="content" source="media/observability/diag-setting-log-analytics-console-log.png" alt-text="Screenshot diagnostic settings Log Analytics destination.":::
     - **Archive to a storage account**: This option is deprecated.
-    - **Stream to an event hub**:  Select from Azure event hubs.  
+    - **Stream to an event hub**: Select from Azure event hubs. 
     :::image type="content" source="media/observability/diag-settings-event-hub.png" alt-text="Screenshot Diagnostic settings event hub destination.":::
-    - **Send to a partner solution**: Select from Azure partner solutions.  
+    - **Send to a partner solution**: Select from Azure partner solutions. 
 1. Select **Save**.
 
 For more information about Diagnostic settings, see [Diagnostic settings in Azure Monitor](/azure/azure-monitor/essentials/diagnostic-settings).
 
 ## Configure options using the Azure CLI
 
-Configure logs destination for your Container Apps environment using the Azure CLI `az containerapp create` and `az containerapp update` commands with the `--logs-destination` argument.  
+Configure logs destination for your Container Apps environment using the Azure CLI `az containerapp create` and `az containerapp update` commands with the `--logs-destination` argument. 
 
 The destination values are: `log-analytics`, `azure-monitor`, and `none`.
 
-For example, to create a Container Apps environment using an existing Log Analytics workspace as the logs destination, you must provide the `--logs-destination` argument with the value `log-analytics` and the `--logs-destination-id` argument with the value of the Log Analytics workspace resource ID.  You can get the resource ID from the Log Analytics workspace page in the Azure portal or from the ```az monitor log-analytics workspace show``` command.
+For example, to create a Container Apps environment using an existing Log Analytics workspace as the logs destination, you must provide the `--logs-destination` argument with the value `log-analytics` and the `--logs-destination-id` argument with the value of the Log Analytics workspace resource ID. You can get the resource ID from the Log Analytics workspace page in the Azure portal or from the ```az monitor log-analytics workspace show``` command.
 
 Replace \<PLACEHOLDERS\> with your values:
 
@@ -102,7 +102,7 @@ az containerapp env update \
   --logs-destination azure-monitor
 ```
 
-When  `--logs-destination` is set to `azure-monitor`, create diagnostic settings to configure the destination details for the log categories with the `az monitor diagnostics-settings` command.  
+When `--logs-destination` is set to `azure-monitor`, create diagnostic settings to configure the destination details for the log categories with the `az monitor diagnostics-settings` command. 
 
 To send app-level metrics to Log Analytics:
 
@@ -116,7 +116,7 @@ az monitor diagnostic-settings create \
 --workspace <LOG_ANALYTICS_ARM_RESOURCE_ID>
 ```
 
-For more information about Azure Monitor diagnostic settings commands, see [az monitor diagnostic-settings](/cli/azure/monitor/diagnostic-settings).  Container Apps log categories are `ContainerAppConsoleLogs` and `ContainerAppSystemLogs`.
+For more information about Azure Monitor diagnostic settings commands, see [az monitor diagnostic-settings](/cli/azure/monitor/diagnostic-settings). Container Apps log categories are `ContainerAppConsoleLogs` and `ContainerAppSystemLogs`.
 
 
 ## Next steps