Gangams/troubelshooting script for arc k8s

scripts/troubleshoot/README.md

@@ -1,5 +1,14 @@
 # Troubleshoot Guide for Azure Monitor for containers
 
+# Azure Arc-enabled Kubernetes
+The table below summarizes known issues you may face while using Azure Monitor for containers .
+
+| Issues and Error Messages  | Action |
+| ---- | --- |
+| Error Message `No data for selected filters`  | It may take some time to establish monitoring data flow for newly created clusters. Please allow at least 10-15 minutes for data to appear for your cluster. |
+| Error Message `Error retrieving data` | While Azure Arc-enabled Kubernetes cluster is setting up for health and performance monitoring, a connection is established between the cluster and Azure Log Analytics workspace. Log Analytics workspace is used to store all monitoring data for your cluster. This error may occurr when your Log Analytics workspace has been deleted or lost. Please check whether your Log Analytics workspace is available. To find your Log Analytics workspace go [here.](https://docs.microsoft.com/en-us/azure/log-analytics/log-analytics-manage-access) and your workspace is available. If the workspace is missing, you will have to delete and create Microsoft.AzureMonitor.Containers extension https://docs.microsoft.com/en-us/azure/azure-monitor/containers/container-insights-enable-arc-enabled-clusters?toc=/azure/azure-arc/kubernetes/toc.json. |
+
+
 # Azure Kubernetes Service (AKS)
 The table below summarizes known issues you may face while using Azure Monitor for containers .
 
@@ -67,5 +76,26 @@ Please send this file to [AskCoin](mailto:askcoin@microsoft.com). We will respon
 For more details on Azure Resource Manager template deployment via cli refer to [this documentation](https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-template-deploy-cli).
 
 If steps above did not help to resolve your issue, you can use either of the following methods to contact us for help:
-*	File a [GitHub Issue](https://github.com/Microsoft/OMS-docker/issues)
+*	File a [GitHub Issue](https://github.com/microsoft/Docker-Provider/issues)
 *	Email [AskCoin](mailto:askcoin@microsoft.com) : Please attach the TroubleshootErrorDump.txt in the email generated by the troubleshooting script if you had tried running the script to solve your problem.
+
+# Azure Arc-enabled Kubernetes
+
+You can use the troubleshooting script provided [here](https://raw.githubusercontent.com/microsoft/Docker-Provider/ci_dev/scripts/troubleshoot/troubleshooterrors.sh) to diagnose the problem.
+
+Steps:
+- Before executing the Troubleshooting script, please install following pre-requisistes if you dont have already
+   - Install [Azure-CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli)
+   - Install [kubectl](https://kubernetes.io/docs/tasks/tools/#kubectl)
+   - Install [jq](https://stedolan.github.io/jq/download/)
+- Download and execute the script
+  ``` bash
+     curl -LO https://raw.githubusercontent.com/microsoft/Docker-Provider/ci_dev/scripts/troubleshoot/troubleshooterrors.sh
+     bash troubleshooterrors.sh --resource-id <azureArcK8sConnectedClusterResourceId> --kube-context <kubeContextofK8sCluster>
+  ```
+- This script will generate a TroubleshootDump.log which collects detailed information about container health onboarding.
+Please send this file to [AskCoin](mailto:askcoin@microsoft.com). We will respond back to you.
+
+If steps above did not help to resolve your issue, you can use either of the following methods to contact us for help:
+*	File a [GitHub Issue](https://github.com/microsoft/Docker-Provider/issues)
+*	Email [AskCoin](mailto:askcoin@microsoft.com) : Please attach the TroubleshootErrorDump.log in the email generated by the troubleshooting script if you had tried running the script to solve your problem.