Merge pull request #250404 from osalzberg/docs-editor/azure-monitor-data-explorer-pr-1693982776

Added examples to ARG query

Author: v-ccolin

articles/azure-monitor/logs/azure-monitor-data-explorer-proxy.md

@@ -6,8 +6,8 @@ ms.author: guywild
 ms.topic: conceptual
 ms.date: 08/22/2023
 ms.reviewer: osalzberg
-
 ---
+
 # Query data in Azure Data Explorer and Azure Resource Graph from Azure Monitor
 Azure Monitor lets you query data in [Azure Data Explorer](/azure/data-explorer/data-explorer-overview) and [Azure Resource Graph](../../governance/resource-graph/overview.md) from your Log Analytics workspace and Application Insights resources. This article explains how to query data in Azure Resource Graph and Azure Data Explorer from Azure Monitor.
 
@@ -51,7 +51,8 @@ union customEvents, adx('https://help.kusto.windows.net/Samples').StormEvents
 ```kusto
 let CL1 = adx('https://help.kusto.windows.net/Samples').StormEvents;
 union customEvents, CL1 | take 10
-```
+
+```sql
 
 > [!TIP]
 > Shorthand format is allowed: *ClusterName*/*InitialCatalog*. For example, `adx('help/Samples')` is translated to `adx('help.kusto.windows.net/Samples')`.
@@ -60,7 +61,7 @@ When you use the [`join` operator](/azure/data-explorer/kusto/query/joinoperator
 
 For example:
 
-```kusto
+kusto
 AzureDiagnostics
 | join hint.remote=left adx("cluster=ClusterURI").AzureDiagnostics on (ColumnName)
 ```
@@ -90,6 +91,49 @@ For example:
 arg("").<Azure-Resource-Graph-table-name>
 ```
 
+Here are some sample Azure Log Analytics queries that use the new Azure Resource Graph cross-service query capabilities:
+
+- Filter a Log Analytics query based on the results of an Azure Resource Graph query:
+
+```kusto
+arg("").Resources 
+| where type == "microsoft.compute/virtualmachines" and properties.hardwareProfile.vmSize startswith "Standard_D"
+| join (
+    Heartbeat
+    | where TimeGenerated > ago(1d)
+    | distinct Computer
+    )
+    on $left.name == $right.Computer
+```
+
+- Create an alert rule that applies only to certain resources taken from an ARG query:
+   - Exclude resources based on tags – for example, not to trigger alerts for VMs with a “Test” tag.
+
+```kusto
+arg("").Resources
+| where tags.environment=~'Test'
+| project name 
+
+```
+
+- Retrieve performance data related to CPU utilization and filter to resources with the “prod” tag.
+
+```kusto
+InsightsMetrics
+| where Name == "UtilizationPercentage"
+| lookup (
+    arg("").Resources 
+    | where type == 'microsoft.compute/virtualmachines' 
+    | project _ResourceId=tolower(id), tags
+    )
+    on _ResourceId
+| where tostring(tags.Env) == "Prod"
+```
+
+More use cases:
+-	Use a tag to determine whether VMs should be running 24x7 or should be shut down at night.
+-	Show alerts on any server that contains a certain number of cores.
+
 ### Combine Azure Resource Graph tables with a Log Analytics workspace
 
 Use the `union` command to combine cluster tables with a Log Analytics workspace.
@@ -103,14 +147,16 @@ union AzureActivity, arg("").Resources
 ```kusto
 let CL1 = arg("").Resources ;
 union AzureActivity, CL1 | take 10
-```
+
+```sql
 
 When you use the [`join` operator](/azure/data-explorer/kusto/query/joinoperator) instead of union, you're required to use a [`hint`](/azure/data-explorer/kusto/query/joinoperator#join-hints) to combine the data in Azure Resource Graph with the Log Analytics workspace. Use `Hint.remote={Direction of the Log Analytics Workspace}`. For example:
 
-```kusto
+kusto
 Perf | where ObjectName == "Memory" and (CounterName == "Available MBytes Memory")
 | extend _ResourceId = replace_string(replace_string(replace_string(_ResourceId, 'microsoft.compute', 'Microsoft.Compute'), 'virtualmachines','virtualMachines'),"resourcegroups","resourceGroups")
 | join hint.remote=left (arg("").Resources | where type =~ 'Microsoft.Compute/virtualMachines' | project _ResourceId=id, tags) on _ResourceId | project-away _ResourceId1 | where tostring(tags.env) == "prod"
+
 ```
 
 ## Create an alert based on a cross-service query
@@ -127,3 +173,5 @@ To create a new alert rule based on a cross-service query, follow the steps in [
 ## Next steps
 * [Write queries](/azure/data-explorer/write-queries)
 * [Perform cross-resource log queries in Azure Monitor](../logs/cross-workspace-query.md)
+
+