Skip to content

Commit 2a4d05d

Browse files
committed
Minot tweaks based on Acrolinx suggestions
1 parent 9b70abc commit 2a4d05d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/managed-grafana/how-to-use-reporting-and-image-rendering.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ Image rendering is a CPU-intensive operation. An Azure Managed Grafana instance
2424
> [!NOTE]
2525
> You'll see a "Image Rendering Timeout" error if a rendering request has exceeded the 200 second limit.
2626

27-
For screen-capturing in alerts, the Grafana software only allows 30 seconds to snapshot panel images before timing out. At most 3 screenshots can be taken within this time frame. If there is a sudden surge in alert volume, some alerts won't have screenshots even if screen-capturing has been enabled.
27+
For screen-capturing in alerts, the Grafana software only allows 30 seconds to snapshot panel images before timing out. At most three screenshots can be taken within this time frame. If there's a sudden surge in alert volume, some alerts may not have screenshots even if screen-capturing has been enabled.
2828

2929
> [!NOTE]
3030
> Overloading the Grafana image renderer may cause it to become unstable. You can reduce the number of alerts that must include screenshots by only setting the Dashboard UID and Panel ID annotations in those alert rules.

0 commit comments

Comments
 (0)