From aceb21815788f1924df5314af5d5ac3362e08cbe Mon Sep 17 00:00:00 2001 From: Andres Martinez Gotor Date: Mon, 30 May 2022 15:49:42 +0200 Subject: [PATCH] AzureMonitor: Document maximum returned records for Resource Graph (#49801) --- docs/sources/datasources/azuremonitor/_index.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/sources/datasources/azuremonitor/_index.md b/docs/sources/datasources/azuremonitor/_index.md index 0ce92c5a9ee..a9e09cf2d03 100644 --- a/docs/sources/datasources/azuremonitor/_index.md +++ b/docs/sources/datasources/azuremonitor/_index.md @@ -272,6 +272,10 @@ You can use Grafana macros when constructing a query. Use the macros in the wher If using the `All` option, then check the `Include All Option` checkbox and in the `Custom all value` field type in the following value: `all`. If `$myVar` has value `all` then the macro will instead expand to `1 == 1`. For template variables with a lot of options, this will increase the query performance by not building a large "where..in" clause. +### Working with large Azure resource data sets + +If a request exceeds the [maximum allowed value of records](https://docs.microsoft.com/en-us/azure/governance/resource-graph/concepts/work-with-data#paging-results), the result is paginated and only the first page of results are returned. You can use filters to reduce the amount of records returned under that value. + ## Going further with Azure Monitor See the following topics to learn more about the Azure Monitor data source: