Skip to content

Commit 8a53fec

Browse files
author
Sreekanth Iyer (Ushta Te Consultancy Services)
committed
Added high res images
1 parent 5ebb161 commit 8a53fec

File tree

3 files changed

+0
-4
lines changed

3 files changed

+0
-4
lines changed

articles/hdinsight/azure-monitor-agent.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -138,10 +138,6 @@ Default queries to use with new tables
138138

139139
In your Logs query editor, set the toggle to Queries above the tables list. Make sure that you group the queries by Resource Type and that there's no filter set for a resource type other than HDInsight Clusters. The following image shows how the results look when grouped by Resource Type and filtered for HDInsight Clusters. Just select one and it appears in the Logs query editor. Be sure to read the comments included in the queries, as some require you to enter some information, like your cluster name, for the query to run successfully.
140140

141-
These integrations can help you use the new tables:
142-
143-
:::image type="content" source="./media/azure-monitor-agent/list-of-queries.png" alt-text="Screenshot showing list of queries." border="true" lightbox="./media/azure-monitor-agent/list-of-queries.png":::
144-
145141
### Create your own queries
146142

147143
You can enter your own queries in the Logs query editor. Queries used on the old tables won't be valid on the new tables as many of the new tables have new, refined schemas. The default queries are great references for shaping queries on the new tables.
-81.8 KB
Loading
Binary file not shown.

0 commit comments

Comments
 (0)