Skip to content

Commit 778e3ec

Browse files
authored
Merge pull request #97798 from MGoedtel/UpdateAzMonCI1204
added troubleshooting section
2 parents 4be1dfa + 4601396 commit 778e3ec

File tree

2 files changed

+21
-2
lines changed

2 files changed

+21
-2
lines changed

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

Lines changed: 20 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.subservice:
66
ms.topic: conceptual
77
author: mgoedtel
88
ms.author: magoedte
9-
ms.date: 10/15/2019
9+
ms.date: 12/04/2019
1010
---
1111

1212
# Configure hybrid Kubernetes clusters with Azure Monitor for containers
@@ -278,6 +278,25 @@ After you have successfully deployed the chart, you can review the data for your
278278
>[!NOTE]
279279
>Ingestion latency is around five to ten minutes from agent to commit in the Azure Log Analytics workspace. Status of the cluster show the value **No data** or **Unknown** until all the required monitoring data is available in Azure Monitor.
280280
281+
## Troubleshooting
282+
283+
If you encounter an error while attempting to enable monitoring for your hybrid Kubernetes cluster, copy the PowerShell script [TroubleshootError_nonAzureK8s.ps1](https://raw.githubusercontent.com/microsoft/OMS-docker/ci_feature/Troubleshoot/TroubleshootError_nonAzureK8s.ps1) and save it to a folder on your computer. This script is provided to help detect and fix the issues encountered. The issues it is designed to detect and attempt correction of are the following:
284+
285+
* The specified Log Analytics workspace is valid
286+
* The Log Analytics workspace is configured with the Azure Monitor for Containers solution. If not, configure the workspace.
287+
* OmsAgent replicaset pod are running
288+
* OmsAgent daemonset pod are running
289+
* OmsAgent Health service is running
290+
* The Log Analytics workspace Id and key configured on the containerized agent match with the workspace the Insight is configured with.
291+
* Validate all the Linux worker nodes have `kubernetes.io/role=agent` label to schedule rs pod. If it doesn't exist, add it.
292+
* Validate `cAdvisor port: 10255` is opened on all nodes in the cluster.
293+
294+
To execute with Azure PowerShell, use the following commands in the folder that contains the script:
295+
296+
```powershell
297+
.\TroubleshootError_nonAzureK8s.ps1 - azureLogAnalyticsWorkspaceResourceId </subscriptions/<subscriptionId>/resourceGroups/<resourcegroupName>/providers/Microsoft.OperationalInsights/workspaces/<workspaceName> -kubeConfig <kubeConfigFile>
298+
```
299+
281300
## Next steps
282301

283302
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) Azure Monitor for containers.

articles/azure-monitor/insights/container-insights-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ Azure Monitor for containers delivers a comprehensive monitoring experience usin
4545
* Monitor container workloads [deployed to Azure Red Hat OpenShift](../../openshift/intro-openshift.md).
4646

4747
>[!NOTE]
48-
>Support for Red Hat OpenShift is a feature in public preview at this time.
48+
>Support for Azure Red Hat OpenShift is a feature in public preview at this time.
4949
>
5050
5151
Check out the following video providing an intermediate level deep dive to help you learn about monitoring your AKS cluster with Azure Monitor for containers.

0 commit comments

Comments
 (0)