edit formatting, indents

Author: GitHubber17

articles/hdinsight/selective-logging-analysis.md

@@ -1,13 +1,13 @@
 ---
-title: Use Selective logging feature using script action in Azure HDInsight clusters 
+title: Use selective logging feature with script action in Azure HDInsight clusters 
 description: Learn how to use Selective logging feature using script action to monitor logs.
 ms.service: hdinsight
 ms.topic: how-to
 ms.custom: seoapr2020, devx-track-azurepowershell, references-regions, devx-track-azurecli
 ms.date: 07/31/2022
 ---
 
-# Learn how to use selective logging feature using script action in Azure HDInsight
+# Learn how to use selective logging feature with script action in Azure HDInsight
 
 [Azure Monitor logs](../azure-monitor/logs/log-query-overview.md) is an Azure Monitor service that monitors your cloud and on-premises environments. The monitoring is to maintain their availability and performance. It collects data generated by resources in your cloud, on-premises environments and from other monitoring tools. The data is used to provide analysis across multiple sources by enabling selective logging feature using script action in Azure portal in HDInsight.
 
@@ -28,76 +28,77 @@ Selective logging allows you to enable/disable all the tables or enable selectiv
 ## Prerequisites
 
 * A Log Analytics workspace. You can think of this workspace as a unique Azure Monitor logs environment with its own data repository, data sources, and solutions. For the instructions, see  [Create a Log Analytics workspace](../azure-monitor/vm/monitor-virtual-machine.md).
-
 * An Azure HDInsight cluster. Currently, you can use selective logging feature with the following HDInsight cluster types:
+   * Hadoop
+   * HBase
+   * Interactive Query
+   * Spark
 
-  * Hadoop
-  * HBase
-  * Interactive Query
-  * Spark
-
-  For the instructions on how to create an HDInsight cluster, see [Get started with Azure HDInsight](hadoop/apache-hadoop-linux-tutorial-get-started.md).  
+For the instructions on how to create an HDInsight cluster, see [Get started with Azure HDInsight](hadoop/apache-hadoop-linux-tutorial-get-started.md).  
 
 ## Enable/disable logs using script action for multiple tables and log types
 
 1. Go to script action in your cluster and create a new Script Action for disabling/enabling table and log type.
 
-:::image type="content" source="./media/hdinsight-hadoop-oms-selective-log-analytics-tutorial/select-submit-script-action.png" alt-text="Screenshot showing select submit script action.":::
+    :::image type="content" source="./media/hdinsight-hadoop-oms-selective-log-analytics-tutorial/select-submit-script-action.png" alt-text="Screenshot showing select submit script action.":::
 
-:::image type="content" source="./media/hdinsight-hadoop-oms-selective-log-analytics-tutorial/submit-script-action-window.png" alt-text="Screenshot showing submit script action window.":::
+    :::image type="content" source="./media/hdinsight-hadoop-oms-selective-log-analytics-tutorial/submit-script-action-window.png" alt-text="Screenshot showing submit script action window.":::
 
-1. In the script type we can select **custom**.
-1. Name the script. For example, Disable two tables and two sources.
+1. In the script type, select **custom**.
+1. Name the script. For example, **Disable two tables and two sources**.
 1. Bash Script URL must be the link of the [selectiveLoggingScript.sh](https://hdiconfigactions.blob.core.windows.net/log-analytics-patch/selectiveLoggingScripts/selectiveLoggingScript.sh).
 1. Select all the nodes of the cluster. For example, Head Node, Worker node, Zookeepr node.
-1. Define the parameters in the parameter box. For example,
-  1. for Spark `spark HDInsightSparkLogs:SparkExecutorLog --disable`
-  1. for Interactivehive `interactivehive HDInsightSparkLogs:SparkExecutorLog --enable`
-  1. for Hadoop `hadoop HDInsightSparkLogs:SparkExecutorLog --disable`
-  1. for HBase  `hbase HDInsightSparkLogs: HDInsightHBaseLogs   --enable`
+1. Define the parameters in the parameter box. For example:
+   - Spark: `spark HDInsightSparkLogs:SparkExecutorLog --disable`
+   - Interactivehive: `interactivehive HDInsightSparkLogs:SparkExecutorLog --enable`
+   - Hadoop: `hadoop HDInsightSparkLogs:SparkExecutorLog --disable`
+   - HBase: `hbase HDInsightSparkLogs: HDInsightHBaseLogs   --enable`
 
-For more details, see [Parameters](#parameters-syntax) section.
+   For more details, see [Parameters](#parameters-syntax) section.
 
 1. Select Create.
-1. After 1-2 minutes you'll see a green tick next to your script action history, which means script has successfully run.
+1. After a few minutes, you'll see a green tick next to your script action history, which means script has successfully run.
 
-:::image type="content" source="./media/hdinsight-hadoop-oms-selective-log-analytics-tutorial/enable-table-and-log-types.png" alt-text="Screenshot showing enable table and log types.":::
+    :::image type="content" source="./media/hdinsight-hadoop-oms-selective-log-analytics-tutorial/enable-table-and-log-types.png" alt-text="Screenshot showing enable table and log types.":::
 
-1. You will see the desired changes in the log analytics workspace.
+You will see the desired changes in the log analytics workspace.
 
 ## Troubleshooting
+
 ### Scenario 1
 
 If Script Action is submitted but there are no changes in the log analytics workspace.
 
 1. Go to Ambari Home and check debug information.
 
-:::image type="content" source="./media/hdinsight-hadoop-oms-selective-log-analytics-tutorial/select-dashboard-ambari-home.png" alt-text="Screenshot showing select dashboard ambari home.":::
+    :::image type="content" source="./media/hdinsight-hadoop-oms-selective-log-analytics-tutorial/select-dashboard-ambari-home.png" alt-text="Screenshot showing select dashboard ambari home.":::
 
 1. Select settings button.
 
-:::image type="content" source="./media/hdinsight-hadoop-oms-selective-log-analytics-tutorial/ambari-dash-board.png" alt-text="Screenshot showing ambari dash board.":::
+    :::image type="content" source="./media/hdinsight-hadoop-oms-selective-log-analytics-tutorial/ambari-dash-board.png" alt-text="Screenshot showing ambari dash board.":::
 
 1. You will get your latest script run at the top of the list.
 
-:::image type="content" source="./media/hdinsight-hadoop-oms-selective-log-analytics-tutorial/background-operations.png" alt-text="Screenshot showing background operations.":::
+    :::image type="content" source="./media/hdinsight-hadoop-oms-selective-log-analytics-tutorial/background-operations.png" alt-text="Screenshot showing background operations.":::
 
 1. Verify the script run status in all the nodes individually.
 
-:::image type="content" source="./media/hdinsight-hadoop-oms-selective-log-analytics-tutorial/background-operations-all.png" alt-text="Screenshot showing background operations all.":::
+    :::image type="content" source="./media/hdinsight-hadoop-oms-selective-log-analytics-tutorial/background-operations-all.png" alt-text="Screenshot showing background operations all.":::
 
 1. Check if the parameter syntax from the parameter syntax section is correct.
 1. Check if the log analytics workspace is connected to the cluster and log analytics monitoring is turned on.
 1. Check if the script that you run from script action was checked as persisted.
 
-:::image type="content" source="./media/hdinsight-hadoop-oms-selective-log-analytics-tutorial/script-action-persists.png" alt-text="Screenshot showing script action persists.":::
+    :::image type="content" source="./media/hdinsight-hadoop-oms-selective-log-analytics-tutorial/script-action-persists.png" alt-text="Screenshot showing script action persists.":::
 
 1. It's possible, that a new node has been added to the cluster recently.
-  > [!NOTE]  
-  > For the script to run in the latest cluster,  and  the script must persist the script.
+
+    > [!NOTE]  
+    > For the script to run in the latest cluster,  and  the script must persist the script.
+   
 1. Make sure all the node types are selected while running  the script action.
 
-:::image type="content" source="./media/hdinsight-hadoop-oms-selective-log-analytics-tutorial/select-node-types.png" alt-text="Screenshot showing select node types.":::
+    :::image type="content" source="./media/hdinsight-hadoop-oms-selective-log-analytics-tutorial/select-node-types.png" alt-text="Screenshot showing select node types.":::
 
 ### Scenario 2
 
@@ -107,7 +108,7 @@ If the script action is showing a Failed status in the script action history
 1. Check that the script link is correct.
 1. Correct link for the script: https://hdiconfigactions.blob.core.windows.net/log-analytics-patch/selectiveLoggingScripts/selectiveLoggingScript.sh
 
-## Table Names
+## Table names
 
 ### Spark cluster
 
@@ -172,10 +173,10 @@ Parameters define the cluster type, table names, source names and the action.
 
 :::image type="content" source="./media/hdinsight-hadoop-oms-selective-log-analytics-tutorial/parameter-syntax-box.png" alt-text="Screenshot showing parameter syntax box.":::
 
-Parameter contains three parts
-1. Cluster type
-1. Tables and Log types
-1. Action (The action can be either `--disable` or `--enable`.)
+Parameter contains three parts:
+- Cluster type
+- Tables and Log types
+- Action (The action can be either `--disable` or `--enable`.)
 
 * Multiple tables syntax
 Rule: The tables are separated with a (,) or comma.
@@ -187,7 +188,7 @@ For example,
 `hbase HDInsightSecurityLogs, HDInsightAmbariSystemMetrics --enable`
 
 > [!NOTE]  
->The tables are separated with a comma.
+> The tables are separated with a comma.
 
 * Multiple source type/log type
 Rule:The source types/log types are separated with a space.
@@ -207,10 +208,10 @@ spark HDInsightSecurityLogs: AmbariAuditLog AuthLog --disable
 * Multiple tables and source types
 If there are two tables and two source types, which we need to be disabled
 
-1. spark InteractiveHiveMetastoreLog logtype in HDInsightHiveAndLLAPLogs table
-1. hbase InteractiveHiveHSILog logtype in HDInsightHiveAndLLAPLogs table
-1. hadoop HDInsightHiveAndLLAPMetrics table
-1. hadoop HDInsightHiveTezAppStats table
+- Spark: InteractiveHiveMetastoreLog logtype in HDInsightHiveAndLLAPLogs table
+- Hbase: InteractiveHiveHSILog logtype in HDInsightHiveAndLLAPLogs table
+- Hadoop: HDInsightHiveAndLLAPMetrics table
+- Hadoop: HDInsightHiveTezAppStats table
 
 Correct Parameter syntax for such cases would be