added troubleshooting section

Author: MGoedtel

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

@@ -6,7 +6,7 @@ ms.subservice:
 ms.topic: conceptual
 author: mgoedtel
 ms.author: magoedte
-ms.date: 10/15/2019
+ms.date: 12/04/2019
 ---
 
 # Configure hybrid Kubernetes clusters with Azure Monitor for containers
@@ -278,6 +278,19 @@ After you have successfully deployed the chart, you can review the data for your
 >[!NOTE]
 >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. 
 
+## Troubleshooting
+
+If you encounter an error while attempting to enable monitoring for your hybrid Kubernetes cluster, the script [TroubleshootError_nonAzureK8s.ps1](https://raw.githubusercontent.com/microsoft/OMS-docker/ci_feature/Troubleshoot/TroubleshootError_nonAzureK8s.ps1) is provided to help detect and fixe the issues encountered. The issues it is designed to detect and attempt correction of are the following:
+
+* The specified Log Analytics workspace is valid 
+* The Log Analytics workspace is configured with the Azure Monitor for Containers solution. If not, configure the workspace.
+* OmsAgent replicaset pod are running
+* OmsAgent daemonset pod are running
+* OmsAgent Health service is running 
+* The Log Analytics workspace Id and key configured on the containerized agent match with the workspace the Insight is configured with.
+* Validate all the Linux worker nodes have `kubernetes.io/role=agent` label to schedule rs pod. If it doesn't exist, add it.
+* Validate `cAdvisor port: 10255` is opened on all nodes in the cluster.
+
 ## 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) Azure Monitor for containers.