Important: This documentation is about an older version. It's relevant only to the release noted, many of the features and functions have been updated or replaced. Please view the current version.
Use images in notifications
Images in notifications helps recipients of alert notifications better understand why an alert has fired or resolved by including a screenshot of the panel associated with the alert.
Note: This feature is not supported for Mimir or Loki rules, or when Grafana sends alert notifications to an external Alertmanager.
When an alert is fired or resolved Grafana takes a screenshot of the panel associated with the alert. This is determined via the Dashboard UID and Panel ID annotations of the rule. Grafana cannot take a screenshot for alerts that are not associated with a panel.
Because a number of contact points, such as email, do not support uploading screenshots at the time of sending a notification; Grafana can also upload the screenshot to a cloud storage service such as Amazon S3, Azure Blob Storage and Google Cloud Storage, where a link to the uploaded screenshot can be added to the notification. However, if using a cloud storage service is not an option then Grafana can be its own cloud storage service such that the screenshot is available under the same domain as Grafana.
Should either the cloud storage service, or Grafana if acting as its own cloud storage service, be protected by a firewall, gateway service or VPN, then screenshots might not be shown in notifications.
How to choose between uploading screenshots at the time of sending the notification, using a cloud storage service, or using Grafana as its own cloud storage service, depends on which contact points you plan to use and whether you use a firewall, gateway service or VPN.
For example, if a contact point supports uploading images at the time of notification is it not required to use cloud storage. Cloud storage is required when a contact point does not support uploading images at the time of sending a notification, such as email. We don’t recommend using cloud storage if the cloud storage service is behind a firewall, gateway service, or VPN, as screenshots might not be shown in notifications.
Please refer to the table at the end of this page for a list of contact points and their support for images in notifications.
To use images in notifications, Grafana must be set up to use image rendering. You can either install the image rendering plugin or run it as a remote rendering service.
When a screenshot is taken it is saved to the data path. This is where screenshots are stored before being sent in a notification or uploaded to a cloud storage service. Grafana must have write-access to this path. If Grafana cannot write to this path then screenshots cannot be saved to disk and an error will be logged for each failed screenshot attempt.
If using a cloud storage service such as Amazon S3, Azure Blob Storage or Google Cloud Storage, uploaded images need to be accessible outside of a firewall, gateway service or VPN for screenshots to be shown in notifications. Grafana will not delete screenshots from cloud storage. We recommend configuring a retention policy on the bucket to delete screenshots older than 1 month.
If using Grafana as its own cloud storage service then screenshots will be saved to
static_root_path is a configuration option for Grafana and can be found in
defaults.ini. However, like when using a cloud storage service, images need to be accessible outside of a firewall, gateway service or VPN for screenshots to be shown in notifications.
When using Grafana as its own cloud storage service screenshots are copied from data to
static_root_path/img/attachments. Screenshots older than
temp_data_lifetime are deleted from data but not from
static_root_path/images/attachments. To delete screenshots from
static_root_path after a certain amount of time we recommend setting up a CRON job.
Having installed either the image rendering plugin, or set up Grafana to use a remote rendering service, set
# Enable screenshots in notifications. You must have either installed the Grafana image rendering # plugin, or set up Grafana to use a remote rendering service. # For more information on configuration options, refer to [rendering]. capture = false
If screenshots should be uploaded to cloud storage then
upload_external_image_storage should also be set to
# Uploads screenshots to the local Grafana server or remote storage such as Azure, S3 and GCS. Please # see [external_image_storage] for further configuration options. If this option is false, screenshots # will be persisted to disk for up to temp_data_lifetime. upload_external_image_storage = false
[external_image_storage] for instructions on how to configure cloud storage. Grafana will not start if
[external_image_storage] contains missing or invalid configuration.
If Grafana is acting as its own cloud storage then
[upload_external_image_storage] should be set to
true and the
local provider should be set in
Restart Grafana for the changes to take effect.
We recommended that
max_concurrent_screenshots is less than or equal to
concurrent_render_request_limit. The default value for both
# 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. max_concurrent_screenshots = 5
Support for images in contact points
Grafana supports a wide range of contact points with varied support for images in notifications. The table below shows the list of all contact points supported in Grafana and their support for uploading images at the time of sending the notification and images uploaded to cloud storage, including when Grafana is acting as its own cloud storage service.
|Name||Upload image at time of notification||Cloud storage|
|Google Hangouts Chat||No||Yes|
|Slack||No (will be available in 9.4)||Yes|
|Cisco Webex Teams||No||Yes|
- This feature is not supported for Mimir or Loki rules, or when Grafana sends alert notifications to an external Alertmanager.
- When multiple alerts are sent in a single notification a screenshot might be included for each alert. The order the images are shown in random.
- Some contact points support at most one image per notification. In this case, the first image associated with an alert will be attached.
- We don’t recommend using cloud storage if the cloud storage service is behind a firewall, gateway service, or VPN, as screenshots might not be shown in notifications.
If Grafana has been set up to send images in notifications, however notifications are still being received without them, follow the troubleshooting steps below:
- Check that images in notifications has been set up as per the instructions.
- Enable debug logging in Grafana and look for logs with the logger
- If the alert is not associated with a dashboard there will be logs for
Cannot take screenshot for alert rule as it is not associated with a dashboard.
- If the alert is associated with a dashboard, but no panel in the dashboard, there will be logs for
Cannot take screenshot for alert rule as it is not associated with a panel.
- If images cannot be taken because of mis-configuration or an issue with image rendering there will be logs for
Failed to take an imageincluding the Dashboard UID, Panel ID, and the error message.
- Check that the contact point supports images in notifications, and the present configuration, as per the table.
- If the image was uploaded to cloud storage make sure it is public.
- If images are made available via Grafana’s built in web server make sure it is accessible via the Internet.
Grafana provides the following metrics to observe the performance and failure rate of images in notifications.
For example, if a screenshot could not be taken within the expected time (10 seconds) then the counter
grafana_screenshot_failures_total is updated.