You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/governance/resource-graph/concepts/query-language.md
+56-32Lines changed: 56 additions & 32 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,8 @@
1
1
---
2
2
title: Understand the query language
3
3
description: Describes Resource Graph tables and the available Kusto data types, operators, and functions usable with Azure Resource Graph.
4
-
ms.date: 12/18/2023
4
+
ms.date: 01/22/2023
5
5
ms.topic: conceptual
6
-
ms.author: davidsmatlak
7
-
author: davidsmatlak
8
6
---
9
7
10
8
# Understanding the Azure Resource Graph query language
@@ -28,39 +26,65 @@ This article covers the language components supported by Resource Graph:
28
26
29
27
## Resource Graph tables
30
28
31
-
Resource Graph provides several tables for the data it stores about Azure Resource Manager resource
32
-
types and their properties. Some tables can be used with `join` or `union` operators to get
33
-
properties from related resource types. Here's the list of tables available in Resource Graph:
34
-
35
-
|Resource Graph table |Can `join` other tables? |Description |
36
-
|---|---|---|
37
-
|Resources | Yes |The default table if none defined in the query. Most Resource Manager resource types and properties are here. |
38
-
|ResourceContainers | Yes |Includes management group (`Microsoft.Management/managementGroups`), subscription (`Microsoft.Resources/subscriptions`) and resource group (`Microsoft.Resources/subscriptions/resourcegroups`) resource types and data. |
39
-
|AdvisorResources | Yes |Includes resources _related_ to `Microsoft.Advisor`. |
40
-
|AlertsManagementResources | Yes |Includes resources _related_ to `Microsoft.AlertsManagement`. |
41
-
|DesktopVirtualizationResources | Yes |Includes resources _related_ to `Microsoft.DesktopVirtualization`. |
42
-
|ExtendedLocationResources | Yes |Includes resources _related_ to `Microsoft.ExtendedLocation`. |
43
-
|GuestConfigurationResources | Yes |Includes resources _related_ to `Microsoft.GuestConfiguration`. |
44
-
|HealthResources| Yes |Includes resources _related_ to `Microsoft.ResourceHealth/availabilitystatuses`. |
45
-
|IoTSecurityResources | Yes |Includes resources _related_ to `Microsoft.IoTSecurity`. |
46
-
|KubernetesConfigurationResources | Yes |Includes resources _related_ to `Microsoft.KubernetesConfiguration`. |
47
-
|MaintenanceResources | Yes |Includes resources _related_ to `Microsoft.Maintenance`. |
|PolicyResources | Yes |Includes resources _related_ to `Microsoft.PolicyInsights`. |
51
-
|RecoveryServicesResources | Yes |Includes resources _related_ to `Microsoft.DataProtection` and `Microsoft.RecoveryServices`. |
52
-
|SecurityResources | Yes |Includes resources _related_ to `Microsoft.Security`. |
53
-
|ServiceHealthResources | Yes |Includes resources _related_ to `Microsoft.ResourceHealth/events`. |
54
-
|WorkloadMonitorResources | Yes |Includes resources _related_ to `Microsoft.WorkloadMonitor`. |
55
-
56
-
For a complete list, including resource types, go to [Reference: Supported tables and resource types](../reference/supported-tables-resources.md).
29
+
Resource Graph provides several tables for the data it stores about Azure Resource Manager resource types and their properties. Resource Graph tables can be used with the `join` operator to get properties from related resource types.
| Resource Graph table | Can `join` other tables? | Description |
38
+
| --- | --- | --- |
39
+
| AdvisorResources | Yes | Includes resources _related_ to `Microsoft.Advisor`. |
40
+
| AlertsManagementResources | Yes | Includes resources _related_ to `Microsoft.AlertsManagement`. |
41
+
| AppServiceResources | Yes | Includes resources _related_ to `Microsoft.Web`. |
42
+
| AuthorizationResources | Yes | Includes resources _related_ to `Microsoft.Authorization`. |
43
+
| AWSResources | Yes | Includes resources _related_ to `Microsoft.AwsConnector`. |
44
+
| AzureBusinessContinuityResources | Yes | Includes resources _related_ to `Microsoft.AzureBusinessContinuity`. |
45
+
| ChaosResources | Yes | Includes resources _related_ to `Microsoft.Chaos`. |
46
+
| CommunityGalleryResources | Yes | Includes resources _related_ to `Microsoft.Compute`. |
47
+
| DesktopVirtualizationResources | Yes | Includes resources _related_ to `Microsoft.DesktopVirtualization`. |
48
+
| DnsResources | Yes | Includes resources _related_ to `Microsoft.Network`. |
49
+
| EdgeOrderResources | Yes | Includes resources _related_ to `Microsoft.EdgeOrder`. |
50
+
| ElasticsanResources | Yes | Includes resources _related_ to `Microsoft.ElasticSan`. |
51
+
| ExtendedLocationResources | Yes | Includes resources _related_ to `Microsoft.ExtendedLocation`. |
52
+
| FeatureResources | Yes | Includes resources _related_ to `Microsoft.Features`. |
53
+
| GuestConfigurationResources | Yes | Includes resources _related_ to `Microsoft.GuestConfiguration`. |
54
+
| HealthResourceChanges | Yes | Includes resources _related_ to `Microsoft.Resources`. |
55
+
| HealthResources| Yes | Includes resources _related_ to `Microsoft.ResourceHealth`. |
56
+
| InsightsResources | Yes | Includes resources _related_ to `Microsoft.Insights`. |
57
+
| IoTSecurityResources | Yes | Includes resources _related_ to `Microsoft.IoTSecurity` and `Microsoft.IoTFirmwareDefense`. |
58
+
| KubernetesConfigurationResources | Yes | Includes resources _related_ to `Microsoft.KubernetesConfiguration`. |
59
+
| KustoResources | Yes | Includes resources _related_ to `Microsoft.Kusto`. |
60
+
| MaintenanceResources | Yes | Includes resources _related_ to `Microsoft.Maintenance`. |
61
+
| ManagedServicesResources | Yes | Includes resources _related_ to `Microsoft.ManagedServices`. |
62
+
| MigrateResources | Yes | Includes resources _related_ to `Microsoft.OffAzure`. |
63
+
| NetworkResources | Yes | Includes resources _related_ to `Microsoft.Network`. |
64
+
| OrbitalResources | Yes | Includes resources _related_ to `Microsoft.Orbital`. |
65
+
| PatchAssessmentResources| Yes | Includes resources _related_ to Azure Virtual Machines patch assessment `Microsoft.Compute` and `Microsoft.HybridCompute`. |
66
+
| PatchInstallationResources| Yes | Includes resources _related_ to Azure Virtual Machines patch installation `Microsoft.Compute` and `Microsoft.HybridCompute`. |
67
+
| PolicyResources | Yes | Includes resources _related_ to `Microsoft.PolicyInsights`. |
68
+
| RecoveryServicesResources | Yes | Includes resources _related_ to `Microsoft.DataProtection` and `Microsoft.RecoveryServices`. |
69
+
| ResourceChanges | Yes | Includes resources _related_ to `Microsoft.Resources`. |
70
+
| ResourceContainerChanges | Yes | Includes resources _related_ to `Microsoft.Resources`. |
71
+
| ResourceContainers | Yes | Includes management group (`Microsoft.Management/managementGroups`), subscription (`Microsoft.Resources/subscriptions`) and resource group (`Microsoft.Resources/subscriptions/resourcegroups`) resource types and data. |
72
+
| Resources | Yes | The default table if a table isn't defined in the query. Most Resource Manager resource types and properties are here. |
73
+
| SecurityResources | Yes | Includes resources _related_ to `Microsoft.Security`. |
74
+
| ServiceFabricResources | Yes | Includes resources _related_ to `Microsoft.ServiceFabric`. |
75
+
| ServiceHealthResources | Yes | Includes resources _related_ to `Microsoft.ResourceHealth/events`. |
76
+
| SpotResources | Yes | Includes resources _related_ to `Microsoft.Compute`. |
77
+
| SupportResources | Yes | Includes resources _related_ to `Microsoft.Support`. |
78
+
| TagsResources | Yes | Includes resources _related_ to `Microsoft.Resources/tagnamespaces`. |
79
+
80
+
For a list of tables that includes resource types, go to [Azure Resource Graph table and resource type reference](../reference/supported-tables-resources.md).
57
81
58
82
> [!NOTE]
59
83
> _Resources_ is the default table. While querying the _Resources_ table, it isn't required to
60
-
> provide the table name unless `join` or `union` are used. However, the recommended practice is to
84
+
> provide the table name unless `join` or `union` are used. But the recommended practice is to
61
85
> always include the initial table in the query.
62
86
63
-
Use Resource Graph Explorer in the portal to discover what resource types are available in each
87
+
Use Resource Graph Explorer in the portal to discover which resource types are available in each
64
88
table. As an alternative, use a query such as `<tableName> | distinct type` to get a list of
65
89
resource types the given Resource Graph table supports that exist in your environment.
66
90
@@ -170,7 +194,7 @@ Here's the list of KQL tabular operators supported by Resource Graph with specif
|[distinct](/azure/data-explorer/kusto/query/distinctoperator)|[Show resources that contain storage](../samples/starter.md#show-resources-that-contain-storage)||
172
196
|[extend](/azure/data-explorer/kusto/query/extendoperator)|[Count virtual machines by OS type](../samples/starter.md#count-virtual-machines-by-os-type)||
173
-
|[join](/azure/data-explorer/kusto/query/joinoperator)|[Key vault with subscription name](../samples/advanced.md#key-vaults-with-subscription-name)|Join flavors supported: [innerunique](/azure/data-explorer/kusto/query/joinoperator#default-join-flavor), [inner](/azure/data-explorer/kusto/query/joinoperator#inner-join), [leftouter](/azure/data-explorer/kusto/query/joinoperator#left-outer-join). Limit of three `join` in a single query, one of which might be a cross-table `join`. If all cross-table `join` use is between _Resource_ and _ResourceContainers_, then three cross-table `join` are allowed. Custom join strategies, such as broadcast join, aren't allowed. For which tables can use `join`, go to [Resource Graph tables](#resource-graph-tables). |
197
+
|[join](/azure/data-explorer/kusto/query/joinoperator)|[Key vault with subscription name](../samples/advanced.md#key-vaults-with-subscription-name)|Join flavors supported: [innerunique](/azure/data-explorer/kusto/query/joinoperator#default-join-flavor), [inner](/azure/data-explorer/kusto/query/joinoperator#inner-join), [leftouter](/azure/data-explorer/kusto/query/joinoperator#left-outer-join), and [fullouter](/azure/data-explorer/kusto/query/join-fullouter). Limit of three `join` in a single query, one of which might be a cross-table `join`. If all cross-table `join` use is between _Resource_ and _ResourceContainers_, then three cross-table `join` are allowed. Custom join strategies, such as broadcast join, aren't allowed. For which tables can use `join`, go to [Resource Graph tables](#resource-graph-tables). |
174
198
|[limit](/azure/data-explorer/kusto/query/limitoperator)|[List all public IP addresses](../samples/starter.md#list-all-public-ip-addresses)|Synonym of `take`. Doesn't work with [Skip](./work-with-data.md#skipping-records). |
175
199
|[mvexpand](/azure/data-explorer/kusto/query/mvexpandoperator)|| Legacy operator, use `mv-expand` instead. _RowLimit_ max of 400. The default is 128. |
176
200
|[mv-expand](/azure/data-explorer/kusto/query/mvexpandoperator)|[List Azure Cosmos DB with specific write locations](../samples/advanced.md#list-azure-cosmos-db-with-specific-write-locations)|_RowLimit_ max of 400. The default is 128. Limit of 2 `mv-expand` in a single query.|
Copy file name to clipboardExpand all lines: articles/postgresql/flexible-server/concepts-query-store.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -277,8 +277,10 @@ This function discards all statistics gathered in-memory by Query Store (that is
277
277
278
278
279
279
## Limitations and known issues
280
+
[!INCLUDE [Note Query store and Azure storage compability](includes/note-query-store-azure-storage-compability.md)]
280
281
281
-
- If an Azure Database for PostgreSQL flexible server instance has the parameter `default_transaction_read_only` set to on, Query Store doesn't capture any data.
282
+
### Read-only mode
283
+
When an Azure Database for PostgreSQL - Flexible Server instance is in read-only mode, such as when the `default_transaction_read_only` parameter is set to `on`, or if read-only mode is [automatically enabled due to reaching storage capacity](concepts-limits.md#storage), Query Store does not capture any data.
[!INCLUDE [Note Query store and Azure storage compability](includes/note-query-store-azure-storage-compability.md)]
202
+
200
203
## Next steps
201
204
202
205
- If you don't see an extension that you'd like to use, let us know. Vote for existing requests or create new feedback requests in our [feedback forum](https://feedback.azure.com/d365community/forum/c5e32b97-ee24-ec11-b6e6-000d3a4f0da0).
Due to compatibility issues, the Query store and Azure storage extensions can't be enabled at the same time. Users are advised to enable only one of these extensions at a time to ensure proper functioning and avoid potential conflicts.
12
+
13
+
***To use Azure storage**: Disable the query store by setting the parameter `pg_qs.query_capture_mode` to `NONE`. This parameter is dynamic, so no restart is needed.
14
+
15
+
***To use Query store**: Disable the Azure storage extension by issuing `DROP EXTENSION azure_storage;`. Additionally, remove Azure storage from the `shared_preload_libraries`. Restart your database server after this change.
16
+
17
+
These steps are necessary to prevent conflicts and ensure your system operates correctly. We're working to resolve these compatibility issues and will keep you informed of any updates in future releases.
0 commit comments