From 33413b762fc7b81b30b2562e67774092c068c6d3 Mon Sep 17 00:00:00 2001 From: "grafana-delivery-bot[bot]" <132647405+grafana-delivery-bot[bot]@users.noreply.github.com> Date: Tue, 16 Apr 2024 16:08:26 +0100 Subject: [PATCH] [v11.0.x] Docs: Add capture_timeout option (#86351) Docs: Add capture_timeout option (#85340) (cherry picked from commit ce57ce4125e3c7b282442939e3b98b08bacb8d5a) Co-authored-by: Santiago --- docs/sources/setup-grafana/configure-grafana/_index.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/sources/setup-grafana/configure-grafana/_index.md b/docs/sources/setup-grafana/configure-grafana/_index.md index 40b64242da9..d26b77ead9f 100644 --- a/docs/sources/setup-grafana/configure-grafana/_index.md +++ b/docs/sources/setup-grafana/configure-grafana/_index.md @@ -1652,6 +1652,11 @@ For more information about screenshots, refer to [Images in notifications]({{< r Enable screenshots in notifications. This option requires a remote HTTP image rendering service. Please see `[rendering]` for further configuration options. +### capture_timeout + +The timeout for capturing screenshots. If a screenshot cannot be captured within the timeout then the notification is sent without a screenshot. +The maximum duration is 30 seconds. This timeout should be less than the minimum Interval of all Evaluation Groups to avoid back pressure on alert rule evaluation. + ### max_concurrent_screenshots The maximum number of screenshots that can be taken at the same time. This option is different from `concurrent_render_request_limit` as `max_concurrent_screenshots` sets the number of concurrent screenshots that can be taken at the same time for all firing alerts where as concurrent_render_request_limit sets the total number of concurrent screenshots across all Grafana services.