Docs: Add a note on query caching for Cloudwatch datasource (#100180)

This commit is contained in:
Ida Štambuk
2025-02-06 15:02:34 +01:00
committed by GitHub
parent 52db2070a0
commit 57e30633e9
3 changed files with 11 additions and 3 deletions
@@ -356,6 +356,10 @@ The CloudWatch data source can query data from both CloudWatch metrics and Cloud
For details, see the [query editor documentation]({{< relref "./query-editor" >}}).
## Query caching
When you enable [query and resource caching]({{< relref "/administration/data-source-management/#query-and-resource-caching" >}}), Grafana temporarily stores the results of data source queries and resource requests. Query caching is available in CloudWatch Metrics in Grafana Cloud and Grafana Enterprise. It is not available in CloudWatch Logs Insights due to how query results are polled from AWS.
## Use template variables
Instead of hard-coding details such as server, application, and sensor names in metric queries, you can use variables.
@@ -438,7 +442,7 @@ For more information, refer to the AWS documentation for [Service Quotas](https:
The CloudWatch plugin enables you to monitor and troubleshoot applications across multiple regional accounts. Using cross-account observability, you can seamlessly search, visualize and analyze metrics and logs without worrying about account boundaries.
To use this feature, configure in the [AWS console under Cloudwatch Settings](https://aws.amazon.com/blogs/aws/new-amazon-cloudwatch-cross-account-observability/), a monitoring and source account, and then add the necessary IAM permissions as described above.
To use this feature, configure in the [AWS console under CloudWatch Settings](https://aws.amazon.com/blogs/aws/new-amazon-cloudwatch-cross-account-observability/), a monitoring and source account, and then add the necessary IAM permissions as described above.
## CloudWatch Logs data protection