Updated selective loggin page

Author: Sreekanth Iyer (Ushta Te Consultancy Services)

articles/hdinsight/azure-monitor-agent.md

@@ -57,14 +57,14 @@ This document outlines the changes to the Azure Monitor integration and provides
 
 The following sections describe how customers can use the new Azure Monitor Agent integration in different scenarios.  
 
-* The [Activate a new Azure Monitor Agent integration](/log-analytics-migration.md#activate-a-new-azure-monitor-integration) section outlines how to activate and use the new Azure Monitor integration.  
+* The [Activate a new Azure Monitor Agent integration](./log-analytics-migration.md#activate-a-new-azure-monitor-integration) section outlines how to activate and use the new Azure Monitor integration.  
 
 * The [Migrating from Azure Monitor Classic to the new Azure Monitor](./log-analytics-migration.md#migrate-to-the-new-azure-monitor-integration) Agent Integration section includes additional information for users that depend on the older adults Azure Monitor integration. 
 
 > [!NOTE]
 > Customers using Azure Monitor Classic will no longer work after 31 August, 2024.  
 >
-> Clusters with Image<Image Number> with the latest HDInsight API <API Number> will have ability to enable the Azure Monitor Agent integration, and this will be the default setup for customers using <Image number>. 
+> Clusters with Image **Image Number** with the latest HDInsight API **API Number** will have ability to enable the Azure Monitor Agent integration, and this will be the default setup for customers using **Image number**. 
 
 ### Activate a new Azure Monitor Agent integration 
 

articles/hdinsight/selective-logging-analysis.md

@@ -4,7 +4,7 @@ description: Learn how to use the selective logging feature with a script action
 ms.service: hdinsight
 ms.topic: how-to
 ms.custom: references-regions
-ms.date: 09/13/2023
+ms.date: 07/31/2024
 ---
 
 # Use selective logging with a script action in Azure HDInsight
@@ -51,13 +51,13 @@ For instructions on how to create an HDInsight cluster, see [Get started with Az
 
 1. For the script type, select **Custom**.
 1. Name the script. For example: **Disable two tables and two sources**.
-1. The Bash script URI must be a link to [selectiveLoggingScript.sh](https://hdiconfigactions.blob.core.windows.net/log-analytics-patch/selectiveLoggingScripts/selectiveLoggingScript.sh).
+1. The Bash script URI must be a link to [selectiveLoggingScript.sh](https://hdiconfigactions.blob.core.windows.net/log-analytics-patch/selectiveLoggingScriptsAma/selectiveLoggingScript.sh).
 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`
-   - Interactive Query: `interactivehive HDInsightSparkLogs:SparkExecutorLog --enable`
-   - Hadoop: `hadoop HDInsightSparkLogs:SparkExecutorLog --disable`
-   - HBase: `hbase HDInsightSparkLogs: HDInsightHBaseLogs   --enable`
+   - Interactive Query: `interactivehive HDInsightHadoopAndYarnLogs:NodeManager --enable`
+   - Hadoop: `hadoop HDInsightHiveAndLLAPLogs:HiveServer2Log --disable`
+   - HBase: `hbase HDInsightHBaseLogs:HBaseRegionServerLog   --enable`
 
    For more information, see the [Parameter syntax](#parameter-syntax) section.
 
@@ -66,7 +66,7 @@ For instructions on how to create an HDInsight cluster, see [Get started with Az
 
     :::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 your changes in the Log Analytics workspace.
+You see your changes in the Log Analytics workspace.
 
 ## Troubleshooting
 
@@ -110,7 +110,7 @@ If you submit your script action but there are no changes in the Log Analytics w
 If the script action shows a failure status in the script action history:
 
 1. Check that the parameter syntax from the parameter syntax section is correct.
-1. Check that the script link is correct. It should be: `https://hdiconfigactions.blob.core.windows.net/log-analytics-patch/selectiveLoggingScripts/selectiveLoggingScript.sh`.
+1. Check that the script link is correct. It should be: `https://hdiconfigactions.blob.core.windows.net/log-analytics-patch/selectiveLoggingScriptsAma/selectiveLoggingScript.sh`.
 
 ## Table names