From cc088dd6a4d1617d5c78eac1fabb441c2b38ca49 Mon Sep 17 00:00:00 2001 From: "Grot (@grafanabot)" <43478413+grafanabot@users.noreply.github.com> Date: Wed, 14 Jun 2023 12:20:59 -0400 Subject: [PATCH] [v9.5.x] AzureMonitor: Update docs to detail Azure logs query changes (#70087) AzureMonitor: Update docs to detail Azure logs query changes (#69987) Update docs to detail Azure logs query changes (cherry picked from commit 068236c37f769c8041cda99e81eef9845b74723d) Co-authored-by: Andreas Christou --- docs/sources/datasources/azure-monitor/query-editor/index.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/sources/datasources/azure-monitor/query-editor/index.md b/docs/sources/datasources/azure-monitor/query-editor/index.md index 2a2e7690bbd..1937ef56add 100644 --- a/docs/sources/datasources/azure-monitor/query-editor/index.md +++ b/docs/sources/datasources/azure-monitor/query-editor/index.md @@ -129,6 +129,11 @@ The Azure documentation includes resources to help you learn KQL: - [Tutorial: Use Kusto queries in Azure Monitor](https://docs.microsoft.com/en-us/azure/data-explorer/kusto/query/tutorial?pivots=azuremonitor) - [SQL to Kusto cheat sheet](https://docs.microsoft.com/en-us/azure/data-explorer/kusto/query/sqlcheatsheet) +> **Implicit dashboard time range usage:** As of Grafana v9.4.12 and v10.0, all Azure Monitor Logs queries +> will use the specified dashboard or Explore time range by default. +> Any query making use of a time range explicitly specified in the query body will have their query +> executed against the intersection of the two time ranges. For more details on this change, refer to the [Azure Monitor Logs API documentation](https://learn.microsoft.com/en-us/rest/api/loganalytics/dataaccess/query/get?tabs=HTTP#uri-parameters). + This example query returns a virtual machine's CPU performance, averaged over 5ms time grains: ```kusto