edit pass: selective-logging-analysis

ShawnJackson · ShawnJackson · commit e18b57bac596 · 2022-08-16T15:47:54.000-05:00
diff --git a/articles/hdinsight/selective-logging-analysis.md b/articles/hdinsight/selective-logging-analysis.md
@@ -1,23 +1,23 @@
 ---
-title: Use the selective logging feature with a script action in Azure HDInsight clusters 
+title: Use selective logging with a script action in Azure HDInsight clusters 
 description: Learn how to use the selective logging feature with a 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
 ---
 
-# Use the selective logging feature with a script action in Azure HDInsight
+# Use selective logging with a 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 helps maintain their availability and performance. 
 
-Azure Monitor Logs collects data generated by resources in your cloud, resources in on-premises environments, and other monitoring tools. It uses the data to provide analysis across multiple sources. To get the analysis, you enable the selective logging feature by using a script action in the Azure portal in HDInsight.
+Azure Monitor Logs collects data generated by resources in your cloud, resources in on-premises environments, and other monitoring tools. It uses the data to provide analysis across multiple sources. To get the analysis, you enable the selective logging feature by using a script action for HDInsight in the Azure portal.
 
 ## About selective logging
 
-Selective logging is a part of Azure overall monitoring system. After you connect your cluster to a Log Analytics workspace and enable selective logging, you can see logs and metrics like HDInsight security logs, Yarn Resource Manager, and system metrics. You can monitor workloads and see how they're affecting cluster stability. 
+Selective logging is a part of the overall monitoring system in Azure. After you connect your cluster to a Log Analytics workspace and enable selective logging, you can see logs and metrics like HDInsight security logs, Yarn Resource Manager, and system metrics. You can monitor workloads and see how they're affecting cluster stability. 
 
-Selective logging allows you to enable or disable all the tables of selected tables in the Log Analytics workspace. You can adjust the source type for each table.
+Selective logging allows you to enable or disable all the tables, or enable selected tables, in the Log Analytics workspace. You can adjust the source type for each table.
 
 > [!NOTE]  
 > If Log Analytics is reinstalled in a cluster, you'll have to disable all the tables and log types again. Reinstallation resets all the configuration files to their original state.
@@ -55,7 +55,7 @@ For instructions on how to create an HDInsight cluster, see [Get started with Az
 1. Select all the node types that apply for the cluster. The options are head node, worker node, and Zookeeper node.
 1. Define the parameters. For example:
    - Spark: `spark HDInsightSparkLogs:SparkExecutorLog --disable`
-   - Interactivehive: `interactivehive HDInsightSparkLogs:SparkExecutorLog --enable`
+   - Interactive Query: `interactivehive HDInsightSparkLogs:SparkExecutorLog --enable`
    - Hadoop: `hadoop HDInsightSparkLogs:SparkExecutorLog --disable`
    - HBase: `hbase HDInsightSparkLogs: HDInsightHBaseLogs   --enable`
 
@@ -64,7 +64,7 @@ For instructions on how to create an HDInsight cluster, see [Get started with Az
 1. Select **Create**.
 1. After a few minutes, a green check mark appears next to your script action history. It means the 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 that shows a successful run of a script to enable tables and log types.":::
 
 You'll see the desired changes in the Log Analytics workspace.
 
@@ -101,7 +101,7 @@ If you submit your script action but there are no changes in the Log Analytics w
     > [!NOTE]  
     > For the script to run in the latest cluster, the script must persist.
    
-1. Make sure that you seleted all the node types that you wanted for the script action.
+1. Make sure that you selected all the node types that you wanted for the script action.
 
     :::image type="content" source="./media/hdinsight-hadoop-oms-selective-log-analytics-tutorial/select-node-types.png" alt-text="Screenshot that shows selected node types.":::
 
@@ -116,7 +116,7 @@ If the script action shows a **Failed** status in the script action history:
 
 ### Spark cluster
 
-Different log types(sources) inside **Spark** tables
+The following table names are for different log types (sources) inside Spark tables.
 
 | Source number  | Table name  | Log types  | Description  |
 | --- | --- | --- | --- |
@@ -128,38 +128,38 @@ Different log types(sources) inside **Spark** tables
 | 6.  | HDInsightHadoopAnd YarnMetrics  | No log types   | This table contains JMX metrics from the Hadoop and YARN frameworks. It contains all the same JMX metrics as the old Custom Logs tables, plus more metrics that we considered important. We added Timeline Server, Node Manager, and Job History Server metrics. It contains one metric per record.  |
 | 7.  | HDInsightOozieLogs  | Oozie  | This table contains all logs generated from the Oozie framework.  |
 
-### Interactive query cluster
+### Interactive Query cluster
 
-Different log types(sources) inside **interactive query** tables
+The following table names are for different log types (sources) inside Interactive Query tables.
 
 | Source number  | Table name  | Log types  | Description  |
 | --- | --- | --- | --- |
 | 1.  | HDInsightAmbariClusterAlerts   | No log types  | This table contains Ambari cluster alerts from each node in the cluster (except for edge nodes). Each alert is a record in this table.  |
 | 2.  | HDInsightAmbariSystem Metrics  | No log types  | This table contains system metrics collected from Ambari. The metrics now come from each node in the cluster (except for edge nodes) instead of just the two head nodes. Each metric is now a column, and each metric is reported once per record.  |
-| 3.  | HDInsightHadoopAndYarnLogs   | **Head node** : MRJobSummary, Resource Manager, TimelineServer   **Worker node:** NodeManager  | This table contains all logs generated from the Hadoop and YARN frameworks.  |
+| 3.  | HDInsightHadoopAndYarnLogs   | **Head node**: MRJobSummary, Resource Manager, TimelineServer   **Worker node**: NodeManager  | This table contains all logs generated from the Hadoop and YARN frameworks.  |
 | 4.  | HDInsightHadoopAndYarnMetrics  | No log types   | This table contains JMX metrics from the Hadoop and YARN frameworks. It contains all the same JMX metrics as the old Custom Logs tables, plus more metrics that we considered important. We added Timeline Server, Node Manager, and Job History Server metrics. It contains one metric per record.  |
 | 5.  | HDInsightHiveAndLLAPLogs   | **Head node**: InteractiveHiveHSILog, InteractiveHiveMetastoreLog, ZeppelinLog    | This table contains logs generated from Hive, LLAP, and their related components: WebHCat and Zeppelin.  |
 | 6.  | HDInsightHiveAndLLAPmetrics   | No log types  | This table contains JMX metrics from the Hive and LLAP frameworks. It contains all the same JMX metrics as the old Custom Logs tables. It contains one metric per record.  |
 | 7.  | HDInsightHiveTezAppStats   | No log types  |
-| 8.  | HDInsightSecurityLogs   | **Head node**: AmbariAuditLog, AuthLog  **Zookeeper node, worker node**: AuthLog  | This table contains records from the Ambari audit and authentication Logs.  |
+| 8.  | HDInsightSecurityLogs   | **Head node**: AmbariAuditLog, AuthLog  **Zookeeper node, worker node**: AuthLog  | This table contains records from the Ambari audit and authentication logs.  |
 
 ### HBase cluster
 
-Different log types(sources) inside **HBase** tables
+The following table names are for different log types (sources) inside HBase tables.
 
 | Source number  | Table name  | Log types  | Description  |
 | --- | --- | --- | --- |
 | 1.  | HDInsightAmbariClusterAlerts   | No other log types  | This table contains Ambari cluster alerts from each node in the cluster (except for edge nodes). Each alert is a record in this table.
 | 2.  | HDInsightAmbariSystem Metrics  | No other log types  | This table contains system metrics collected from Ambari. The metrics now come from each node in the cluster (except for edge nodes) instead of just the two head nodes. Each metric is now a column, and each metric is reported once per record.  |
-| 3.  | HDInsightHadoopAndYarnLogs   | **Head node** : MRJobSummary, Resource Manager, TimelineServer   **Worker node:** NodeManager  | This table contains all logs generated from the Hadoop and YARN frameworks.  |
-| 4.  | HDInsightSecurityLogs   | **Head node:** AmbariAuditLog, AuthLog   **Worker node:** AuthLog  **ZooKeper node:** AuthLog  | This table contains records from the Ambari audit and authentication logs.  |
-| 5.  | HDInsightHBaseLogs   | **Head node** : HDFSGarbageCollectorLog, HDFSNameNodeLog   **Worker node:** PhoenixServerLog, HBaseRegionServerLog, HBaseRestServerLog   **Zookeeper node:** HBaseMasterLog   | This table contains logs from HBase and its related components: Phoenix and HDFS.  |
-| 6.  | HDInsightHBaseMetrics   | No log types  | This table contains JMX metrics from HBase. It contains all the same JMX metrics from the tables listed in the Old Schema column. In contrast from the old tables, each row contains one metric.  |
+| 3.  | HDInsightHadoopAndYarnLogs   | **Head node**: MRJobSummary, Resource Manager, TimelineServer   **Worker node**: NodeManager  | This table contains all logs generated from the Hadoop and YARN frameworks.  |
+| 4.  | HDInsightSecurityLogs   | **Head node**: AmbariAuditLog, AuthLog   **Worker node**: AuthLog  **Zookeeper node**: AuthLog  | This table contains records from the Ambari audit and authentication logs.  |
+| 5.  | HDInsightHBaseLogs   | **Head node**: HDFSGarbageCollectorLog, HDFSNameNodeLog   **Worker node**: PhoenixServerLog, HBaseRegionServerLog, HBaseRestServerLog   **Zookeeper node**: HBaseMasterLog   | This table contains logs from HBase and its related components: Phoenix and HDFS.  |
+| 6.  | HDInsightHBaseMetrics   | No log types  | This table contains JMX metrics from HBase. It contains all the same JMX metrics from the tables listed in the **Old Schema** column. In contrast from the old tables, each row contains one metric.  |
 | 7.  | HDInsightHadoopAndYarn Metrics  | No log types  | This table contains JMX metrics from the Hadoop and YARN frameworks. It contains all the same JMX metrics as the old Custom Logs tables, plus more metrics that we considered important. We added Timeline Server, Node Manager, and Job History Server metrics. It contains one metric per record.  |
 
 ### Hadoop cluster
 
-Different log types(sources) inside Hadoop tables
+The following table names are for different log types (sources) inside Hadoop tables.
 
 | Source number  | Table name  | Log types  | Description  |
 | --- | --- | --- | --- |
@@ -169,7 +169,7 @@ Different log types(sources) inside Hadoop tables
 | 4.  | HDInsightHadoopAndYarnMetrics   |  No Log Types  | This table contains JMX metrics from the Hadoop and YARN frameworks. It contains all the same JMX metrics as the old Custom Logs tables, plus more metrics that we considered important. We added Timeline Server, Node Manager, and Job History Server metrics. It contains one metric per record.  |
 | 5.  | HDInsightHiveAndLLAPLogs    | **Head node**: HiveMetastoreLog, HiveServer2Log, WebHcatLog     | This table contains logs generated from Hive, LLAP, and their related components: WebHCat and Zeppelin.  |
 | 6.  | HDInsight Hive And LLAP Metrics   | No log types   | This table contains JMX metrics from the Hive and LLAP frameworks. It contains all the same JMX metrics as the old Custom Logs tables. It contains one metric per record.  |
-| 7.  | HDInsight Security Logs  | **Head node**: AmbariAuditLog, AuthLog  **Zookeeper node**: AuthLog   | This table contains records from the Ambari audit and authentication Logs.  |
+| 7.  | HDInsight Security Logs  | **Head node**: AmbariAuditLog, AuthLog  **Zookeeper node**: AuthLog   | This table contains records from the Ambari audit and authentication logs.  |
 
 ## Parameter syntax
 
@@ -184,9 +184,7 @@ A parameter contains three parts:
 
 ### Syntax for multiple tables
 
-When you have multiple tables, they're separated with a comma.
-
-For example:
+When you have multiple tables, they're separated with a comma. For example:
 
 `spark HDInsightSecurityLogs, HDInsightAmbariSystemMetrics --disable`
 
@@ -197,21 +195,23 @@ For example:
 When you have multiple source types or log types, they're separated with a space.
 
 To disable a source, write the table name that contains the log types, followed by a colon and then the real log type name:
- `TableName :  LogTypeName`
+
+`TableName :  LogTypeName`
 
 For example, assume that `spark HDInsightSecurityLogs` is a table that has two log types: `AmbariAuditLog` and `AuthLog`. To disable both the log types, the correct syntax would be:
 
 `spark HDInsightSecurityLogs: AmbariAuditLog AuthLog --disable`
 
-### Multiple tables and source types
-If there are two tables and two source types that you need to disable, use the following syntax:
+### Syntax for multiple tables and source types
+
+If you need to disable two tables and two source types, use the following syntax:
 
 - Spark: `InteractiveHiveMetastoreLog` log type in the `HDInsightHiveAndLLAPLogs` table
 - Hbase: `InteractiveHiveHSILog` log type in the `HDInsightHiveAndLLAPLogs` table
 - Hadoop: `HDInsightHiveAndLLAPMetrics` table
 - Hadoop: `HDInsightHiveTezAppStats` table
 
-Separate the tables with a comma. Denote sources by uwing a colon after the table name in which they reside. 
+Separate the tables with a comma. Denote sources by using a colon after the table name in which they reside. 
 
 The correct parameter syntax for these cases would be:
 
