Skip to content

Commit 955f0fd

Browse files
committed
fixed items per discussion with engineer
1 parent cc0c12f commit 955f0fd

File tree

4 files changed

+8
-8
lines changed

4 files changed

+8
-8
lines changed

articles/azure-monitor/insights/container-insights-agent-config.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Configure Azure Monitor for containers agent data collection | Microsoft Docs
33
description: This article describes how you can configure the Azure Monitor for containers agent to control stdout/stderr and environment variables log collection.
44
ms.topic: conceptual
5-
ms.date: 01/10/2020
5+
ms.date: 01/13/2020
66
---
77

88
# Configure agent data collection for Azure Monitor for containers
@@ -12,7 +12,7 @@ Azure Monitor for containers collects stdout, stderr, and environmental variable
1212
This article demonstrates how to create ConfigMap and configure data collection based on your requirements.
1313

1414
>[!NOTE]
15-
>For Azure Red Hat OpenShift, a template ConfigMap file is created in the *openshift-azure-logging* namespace. It is not configured to actively collect data from the agent.
15+
>For Azure Red Hat OpenShift, a template ConfigMap file is created in the *openshift-azure-logging* namespace.
1616
>
1717
1818
## ConfigMap file settings overview
@@ -89,7 +89,7 @@ Errors related to applying configuration changes are also available for review.
8989
9090
- From the **KubeMonAgentEvents** table in your Log Analytics workspace. Data is sent every hour with *Error* severity for configuration errors. If there are no errors, the entry in the table will have data with severity *Info*, which reports no errors. The **Tags** property contains more information about the pod and container ID on which the error occurred and also the first occurrence, last occurrence and count in the last hour.
9191
92-
- For Azure Red Hat OpenShift, check the omsagent logs by searching the **ContainerLog** table to verify if log collection of openshift-azure-logging is enabled.
92+
- With Azure Red Hat OpenShift, check the omsagent logs by searching the **ContainerLog** table to verify if log collection of openshift-azure-logging is enabled.
9393
9494
After you correct the error(s) in ConfigMap on clusters other than Azure Red Hat OpenShift, save the yaml file and apply the updated ConfigMaps by running the command: `kubectl apply -f <configmap_yaml_file.yaml`. For Azure Red Hat OpenShift, edit and save the updated ConfigMaps by running the command:
9595

articles/azure-monitor/insights/container-insights-azure-redhat-setup.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Configure Azure Red Hat OpenShift clusters with Azure Monitor for containers | Microsoft Docs
33
description: This article describes how to configure monitoring of a Kubernetes cluster with Azure Monitor hosted on Azure Red Hat OpenShift.
44
ms.topic: conceptual
5-
ms.date: 01/09/2020
5+
ms.date: 01/13/2020
66
---
77

88
# Configure Azure Red Hat OpenShift clusters with Azure Monitor for containers

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: How to manage the Azure Monitor for containers agent | Microsoft Docs
33
description: This article describes managing the most common maintenance tasks with the containerized Log Analytics agent used by Azure Monitor for containers.
44
ms.topic: conceptual
5-
ms.date: 01/10/2020
5+
ms.date: 01/13/2020
66

77
---
88

@@ -18,15 +18,15 @@ If the agent upgrade fails, this article describes the process to manually upgra
1818

1919
### Upgrading agent on monitored Kubernetes cluster
2020

21-
The process to upgrade the agent consists of two straight forward steps. The first step is to disable monitoring with Azure Monitor for containers using Azure CLI. Follow the steps described in the [Disable monitoring](container-insights-optout.md?#azure-cli) article. Using Azure CLI allows us to remove the agent from the nodes in the cluster without impacting the solution and the corresponding data that is stored in the workspace.
21+
The process to upgrade the agent on clusters, other than Azure Red Hat OpenShift, consists of two straight forward steps. The first step is to disable monitoring with Azure Monitor for containers using Azure CLI. Follow the steps described in the [Disable monitoring](container-insights-optout.md?#azure-cli) article. Using Azure CLI allows us to remove the agent from the nodes in the cluster without impacting the solution and the corresponding data that is stored in the workspace.
2222

2323
>[!NOTE]
2424
>While you are performing this maintenance activity, the nodes in the cluster are not forwarding collected data, and performance views will not show data between the time you remove the agent and install the new version.
2525
>
2626
2727
To install the new version of the agent, follow the steps described in the [enable monitoring using Azure CLI](container-insights-enable-new-cluster.md#enable-using-azure-cli), to complete this process.
2828

29-
After you've re-enabled monitoring, it might take about 15 minutes before you can view updated health metrics for the cluster. To verify the agent upgraded successfully, run the command: `kubectl logs omsagent-484hw --namespace=kube-system`
29+
After you've re-enabled monitoring, it might take about 15 minutes before you can view updated health metrics for the cluster. To verify the agent upgraded successfully, run the command: `kubectl logs omsagent-484hw --namespace=kube-system`
3030

3131
The status should resemble the following example, where the value for *omi* and *omsagent* should match the latest version specified in the [agent release history](https://github.com/microsoft/docker-provider/tree/ci_feature_prod).
3232

articles/azure-monitor/insights/container-insights-prometheus-integration.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Configure Azure Monitor for containers Prometheus Integration | Microsoft Docs
33
description: This article describes how you can configure the Azure Monitor for containers agent to scrape metrics from Prometheus with your Kubernetes cluster.
44
ms.topic: conceptual
5-
ms.date: 01/09/2020
5+
ms.date: 01/13/2020
66
---
77

88
# Configure scraping of Prometheus metrics with Azure Monitor for containers

0 commit comments

Comments
 (0)