Merge pull request #209857 from v-jbasden/jbasden-container-insights-freshness-1

Freshness updates

Author: JamesJBarnett

articles/azure-monitor/containers/container-insights-deployment-hpa-metrics.md

@@ -2,8 +2,8 @@
 title: Deployment & HPA metrics with Container insights | Microsoft Docs
 description: This article describes what deployment & HPA (Horizontal pod autoscaler) metrics are collected with Container insights.
 ms.topic: conceptual
-ms.date: 08/09/2020
-ms.reviewer: aul
+ms.date: 08/29/2022
+ms.reviewer: viviandiec
 ---
 
 # Deployment & HPA metrics with Container insights

articles/azure-monitor/containers/container-insights-enable-aks-policy.md

@@ -2,8 +2,8 @@
 title: Enable AKS Monitoring Addon using Azure Policy
 description: Describes how to enable AKS Monitoring Addon using Azure Custom Policy.
 ms.topic: conceptual
-ms.date: 02/04/2021
-ms.reviewer: aul
+ms.date: 08/29/2022
+ms.reviewer: viviandiec
 ---
 
 # Enable AKS monitoring addon using Azure Policy

articles/azure-monitor/containers/container-insights-hybrid-setup.md

@@ -2,8 +2,8 @@
 title: Configure Hybrid Kubernetes clusters with Container insights | Microsoft Docs
 description: This article describes how you can configure Container insights to monitor Kubernetes clusters hosted on Azure Stack or other environment.
 ms.topic: conceptual
-ms.date: 06/30/2020
-ms.reviewer: aul
+ms.date: 08/29/2022
+ms.reviewer: viviandiec
 ---
 
 # Configure hybrid Kubernetes clusters with Container insights
@@ -317,7 +317,7 @@ Supported API definitions for the Azure Stack Hub cluster can be found in this e
 
 ## Configure agent data collection
 
-Staring with chart version 1.0.0, the agent data collection settings are controlled from the ConfigMap. Refer to documentation about agent data collection settings [here](container-insights-agent-config.md).
+Starting with chart version 1.0.0, the agent data collection settings are controlled from the ConfigMap. Refer to documentation about agent data collection settings [here](container-insights-agent-config.md).
 
 After you have successfully deployed the chart, you can review the data for your hybrid Kubernetes cluster in Container insights from the Azure portal.  
 
@@ -366,4 +366,4 @@ To execute with Azure PowerShell, use the following commands in the folder that
 
 ## Next steps
 
-With monitoring enabled to collect health and resource utilization of your hybrid Kubernetes cluster and workloads running on them, learn [how to use](container-insights-analyze.md) Container insights.
+With monitoring enabled to collect health and resource utilization of your hybrid Kubernetes cluster and workloads running on them, learn [how to use](container-insights-analyze.md) Container insights.

articles/azure-monitor/containers/container-insights-log-alerts.md

@@ -2,8 +2,8 @@
 title: Log alerts from Container insights | Microsoft Docs
 description: This article describes how to create custom log alerts for memory and CPU utilization from Container insights.
 ms.topic: conceptual
-ms.date: 07/29/2021
-ms.reviewer: aul
+ms.date: 08/29/2022
+ms.reviewer: viviandiec
 
 ---
 
@@ -37,7 +37,7 @@ To create resource-centric alerts at scale for a subscription or resource group,
 
 You may also decide not to split when you want a condition on multiple resources in the scope. For example, if you want to create an alert if at least five machines in the resource group scope have CPU usage over 80%.
 
-:::image type="content" source="../vm/media/monitor-virtual-machines/log-alert-rule.png" alt-text="Screenshot of a new log alert rule with split by dimensions.":::
+:::image type="content" source="../vm/media/monitor-virtual-machines/log-alert-rule.png" alt-text="Screenshot of a new log alert rule with split by dimensions." lightbox="../vm/media/monitor-virtual-machines/log-alert-rule.png":::
 
 You might want to see a list of the alerts by affected computer. You can use a custom workbook that uses a custom [Resource Graph](../../governance/resource-graph/overview.md) to provide this view. Use the following query to display alerts, and use the data source **Azure Resource Graph** in the workbook.
 ## Create a log query alert rule

articles/azure-monitor/containers/container-insights-log-query.md

@@ -2,8 +2,8 @@
 title: Query logs from Container insights
 description: Container insights collects metrics and log data, and this article describes the records and includes sample queries.
 ms.topic: conceptual
-ms.date: 07/19/2021
-ms.reviewer: aul
+ms.date: 08/29/2022
+ms.reviewer: viviandiec
 
 ---
 
@@ -309,7 +309,7 @@ KubeMonAgentEvents | where Level != "Info"
 
 The output shows results similar to the following example:
 
-![Screenshot that shows log query results of informational events from an agent.](./media/container-insights-log-query/log-query-example-kubeagent-events.png)
+:::image type="content" source="./media/container-insights-log-query/log-query-example-kubeagent-events.png" alt-text="Screenshot that shows log query results of informational events from an agent." lightbox="media/container-insights-log-query/log-query-example-kubeagent-events.png":::
 
 ## Next steps
 

articles/azure-monitor/containers/container-insights-manage-agent.md

@@ -2,8 +2,8 @@
 title: How to manage the Container insights agent | Microsoft Docs
 description: This article describes managing the most common maintenance tasks with the containerized Log Analytics agent used by Container insights.
 ms.topic: conceptual
-ms.date: 07/21/2020
-ms.reviewer: aul
+ms.date: 08/29/2022
+ms.reviewer: viviandiec
 ---
 
 # How to manage the Container insights agent
@@ -12,9 +12,9 @@ Container insights uses a containerized version of the Log Analytics agent for L
 
 ## How to upgrade the Container insights agent
 
-Container insights uses a containerized version of the Log Analytics agent for Linux. When a new version of the agent is released, the agent is automatically upgraded on your managed Kubernetes clusters hosted on Azure Kubernetes Service (AKS) and Azure Red Hat OpenShift version 3.x. For a [hybrid Kubernetes cluster](container-insights-hybrid-setup.md) and Azure Red Hat OpenShift version 4.x, the agent is not managed, and you need to manually upgrade the agent.
+Container insights uses a containerized version of the Log Analytics agent for Linux. When a new version of the agent is released, the agent is automatically upgraded on your managed Kubernetes clusters hosted on Azure Kubernetes Service (AKS). For a [hybrid Kubernetes cluster](container-insights-hybrid-setup.md), the agent is not managed, and you need to manually upgrade the agent.
 
-If the agent upgrade fails for a cluster hosted on AKS or Azure Red Hat OpenShift version 3.x, this article also describes the process to manually upgrade the agent. To follow the versions released, see [agent release announcements](https://github.com/microsoft/docker-provider/tree/ci_feature_prod).
+If the agent upgrade fails for a cluster hosted on AKS, this article also describes the process to manually upgrade the agent. To follow the versions released, see [agent release announcements](https://github.com/microsoft/docker-provider/tree/ci_feature_prod).
 
 ### Upgrade agent on AKS cluster
 
@@ -59,20 +59,6 @@ If the Log Analytics workspace is in Azure US Government, run the following comm
 $ helm upgrade --set omsagent.domain=opinsights.azure.us,omsagent.secret.wsid=<your_workspace_id>,omsagent.secret.key=<your_workspace_key>,omsagent.env.clusterName=<your_cluster_name> incubator/azuremonitor-containers
 ```
 
-### Upgrade agent on Azure Red Hat OpenShift v4
-
-Perform the following steps to upgrade the agent on a Kubernetes cluster running on Azure Red Hat OpenShift version 4.x. 
-
->[!NOTE]
->Azure Red Hat OpenShift version 4.x only supports running in the Azure commercial cloud.
->
-
-```console
-curl -o upgrade-monitoring.sh -L https://aka.ms/upgrade-monitoring-bash-script
-export azureAroV4ClusterResourceId="/subscriptions/<subscriptionId>/resourceGroups/<resourceGroupName>/providers/Microsoft.RedHatOpenShift/OpenShiftClusters/<clusterName>"
-bash upgrade-monitoring.sh --resource-id $ azureAroV4ClusterResourceId
-```
-
 ## How to disable environment variable collection on a container
 
 Container insights collects environmental variables from the containers running in a pod and presents them in the property pane of the selected container in the **Containers** view. You can control this behavior by disabling collection for a specific container either during deployment of the Kubernetes cluster, or after by setting the environment variable *AZMON_COLLECT_ENV*. This feature is available from the agent version – ciprod11292018 and higher.  
@@ -84,13 +70,7 @@ To disable collection of environmental variables on a new or existing container,
   value: "False"  
 ```
 
-Run the following command to apply the change to Kubernetes clusters other than Azure Red Hat OpenShift): `kubectl apply -f  <path to yaml file>`. To edit ConfigMap and apply this change for Azure Red Hat OpenShift clusters, run the command:
-
-```bash
-oc edit configmaps container-azm-ms-agentconfig -n openshift-azure-logging
-```
-
-This opens your default text editor. After setting the variable, save the file in the editor.
+Run the following command to apply the change to Kubernetes clusters: `kubectl apply -f  <path to yaml file>`.
 
 To verify the configuration change took effect, select a container in the **Containers** view in Container insights, and in the property panel, expand **Environment Variables**.  The section should show only the variable created earlier - **AZMON_COLLECT_ENV=FALSE**. For all other containers, the Environment Variables section should list all the environment variables discovered.