From dc57bcd458076c72035f9955bcf84bc93af8d4e7 Mon Sep 17 00:00:00 2001 From: Andrej Ocenas Date: Tue, 14 Dec 2021 16:18:45 +0100 Subject: [PATCH] Docs: Add CloudWatch Logs retry strategy timeout config (#42485) * Add section for the timeout * Move and remove the table * Change header level --- docs/sources/datasources/aws-cloudwatch/_index.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/sources/datasources/aws-cloudwatch/_index.md b/docs/sources/datasources/aws-cloudwatch/_index.md index 19eb8233b89..7311be8cec5 100644 --- a/docs/sources/datasources/aws-cloudwatch/_index.md +++ b/docs/sources/datasources/aws-cloudwatch/_index.md @@ -79,6 +79,10 @@ Here is a minimal policy example: Grafana is not able to load custom namespaces through the GetMetricData API. If you still want your custom metrics to show up in the fields in the query editor, you can specify the names of the namespaces containing the custom metrics in the _Namespaces of Custom Metrics_ field. The field accepts a multiple namespaces, separated by a comma. +#### Timeout + +Timeout specifically, for CloudWatch Logs queries. Log queries don't recognize standard Grafana query timeout as they don't keep a single request open and instead periodically poll for results. Because of limits on concurrently running queries in CloudWatch they can also take a longer time to finish. + #### X-Ray trace links Link an X-Ray data source in the "X-Ray trace link" section of the configuration page to automatically add links in your logs when the log contains `@xrayTraceId` field.