Merge pull request #89056 from dagiro/cats148

cats148

Author: PRMerger10

articles/hdinsight/kafka/apache-kafka-log-analytics-operations-management.md

@@ -1,10 +1,10 @@
 ---
 title: Azure Monitor logs for Apache Kafka - Azure HDInsight 
 description: Learn how to use Azure Monitor logs to analyze logs from Apache Kafka cluster on Azure HDInsight.
-ms.service: hdinsight
 author: hrasheed-msft
 ms.author: hrasheed
 ms.reviewer: jasonh
+ms.service: hdinsight
 ms.custom: hdinsightactive
 ms.topic: conceptual
 ms.date: 05/02/2019
@@ -38,7 +38,7 @@ The steps to enable Azure Monitor logs for HDInsight are the same for all HDInsi
 * Disk usage:
 
     ```kusto
-    Perf 
+    Perf
     | where ObjectName == "Logical Disk" and CounterName == "Free Megabytes" and InstanceName == "_Total" and ((Computer startswith_cs "hn" and Computer contains_cs "-") or (Computer startswith_cs "wn" and Computer contains_cs "-")) 
     | summarize AggregatedValue = avg(CounterValue) by Computer, bin(TimeGenerated, 1h)
     ```
@@ -77,17 +77,17 @@ The steps to enable Azure Monitor logs for HDInsight are the same for all HDInsi
 
     > [!IMPORTANT]  
     > Replace the query values with your cluster specific information. For example, `ClusterName_s` must be set to the name of your cluster. `HostName_s` must be set to the domain name of a worker node in the cluster.
-    
+
     You can also enter `*` to search all types logged. Currently the following logs are available for queries:
-    
+
     | Log type | Description |
     | ---- | ---- |
     | log\_kafkaserver\_CL | Kafka broker server.log |
     | log\_kafkacontroller\_CL | Kafka broker controller.log |
     | metrics\_kafka\_CL | Kafka JMX metrics |
-    
-    ![Image of the CPU usage search](./media/apache-kafka-log-analytics-operations-management/apache-kafka-cpu-usage.png)
- 
+
+    ![Apache kafka log analytics cpu usage](./media/apache-kafka-log-analytics-operations-management/apache-kafka-cpu-usage.png)
+
 ## Next steps
 
 For more information on Azure Monitor, see [Azure Monitor overview](../../log-analytics/log-analytics-get-started.md), and [Query Azure Monitor logs to monitor HDInsight clusters](../hdinsight-hadoop-oms-log-analytics-use-queries.md).

articles/hdinsight/kafka/apache-kafka-mirroring.md

@@ -79,7 +79,7 @@ This architecture features two clusters in different resource groups and virtual
     1. Click **Add**.
     1. On the **Add peering** screen, enter the details as shown in the screenshot below.
 
-        ![add vnet peering](./media/apache-kafka-mirroring/hdi-add-vnet-peering.png)
+        ![HDInsight Kafka add vnet peering](./media/apache-kafka-mirroring/hdi-add-vnet-peering.png)
 
 1. Configure IP advertising:
     1. Go to the Ambari dashboard for the primary cluster: `https://PRIMARYCLUSTERNAME.azurehdinsight.net`.
@@ -99,7 +99,7 @@ This architecture features two clusters in different resource groups and virtual
     1. Click **Ok** on the **Save Configuration Changes**.
     1. Click **Restart** > **Restart All Affected** in the **Restart Required** notification. Click **Confirm Restart All**.
 
-        ![restart kafka nodes](./media/apache-kafka-mirroring/ambari-restart-notification.png)
+        ![Apache Ambari restart all affected](./media/apache-kafka-mirroring/ambari-restart-notification.png)
 
 1. Configure Kafka to listen on all network interfaces.
     1. Stay on the **Configs** tab under **Services** > **Kafka**. In the **Kafka Broker** section set the **listeners** property to `PLAINTEXT://0.0.0.0:9092`.
@@ -110,7 +110,7 @@ This architecture features two clusters in different resource groups and virtual
     1. Click **Hosts** on the Ambari dashboard.
     1. Make a note of the IP Addresses for the Brokers and Zookeepers. The broker nodes have **wn** as the first two letters of the host name, and the zookeeper nodes have **zk** as the first two letters of the host name.
 
-        ![view ip addresses](./media/apache-kafka-mirroring/view-node-ip-addresses2.png)
+        ![Apache Ambari view node ip addresses](./media/apache-kafka-mirroring/view-node-ip-addresses2.png)
 
 1. Repeat the previous three steps for the second cluster **kafka-secondary-cluster**: configure IP advertising, set listeners and make a note of the Broker and Zookeeper IP addresses.
 
@@ -246,7 +246,7 @@ This architecture features two clusters in different resource groups and virtual
         6. Change the value of `auto.create.topics.enable` to true, and then select __Save__. Add a note, and then select __Save__ again.
         7. Select the __Kafka__ service, select __Restart__, and then select __Restart all affected__. When prompted, select __Confirm restart all__.
 
-        ![configure topic auto creation](./media/apache-kafka-mirroring/kafka-enable-auto-create-topics.png)
+        ![kafka enable auto create topics](./media/apache-kafka-mirroring/kafka-enable-auto-create-topics.png)
 
 ## Start MirrorMaker