You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rendering images requires a lot of memory, mainly because Grafana creates browser instances in the background for the actual rendering.
23
+
We recommend a minimum of 16GB of free memory on the system rendering images.
23
24
24
-
**NOTE:** Installing this plugin using grafana-cli is supported from Grafana v6.4.
25
+
Rendering multiple images in parallel requires an even bigger memory footprint. You can use the remote rendering service in order to render images on a remote system, so your local system resources are not affected.
26
+
27
+
## Plugin installation
28
+
29
+
You can install the plugin using Grafana CLI (recommended way) or with Grafana Docker image.
This plugin is not compatible with the current Grafana Docker image without installing further system-level dependencies. We recommend setting up another Docker container
33
-
for rendering and using remote rendering, see [Remote Rendering Using Docker](#remote-rendering-using-docker) for reference.
39
+
This plugin is not compatible with the current Grafana Docker image and requires additional system-level dependencies. We recommend setting up another Docker container for rendering and using remote rendering instead. For instruction, refer to [Run in Docker](#run-in-docker).
34
40
35
-
If you still want to install the plugin in the Grafana docker image we provide instructions for how to build a custom Grafana image, see[Grafana Docker documentation](https://grafana.com/docs/installation/docker/#custom-image-with-grafana-image-renderer-plugin-pre-installed) for further instructions.
41
+
If you still want to install the plugin with the Grafana Docker image, refer to the instructions on building a custom Grafana image in[Grafana Docker documentation](https://grafana.com/docs/installation/docker/#custom-image-with-grafana-image-renderer-plugin-pre-installed).
36
42
43
+
## Remote rendering service installation
37
44
38
-
### Configuration
45
+
> **Note:** Requires an internet connection.
39
46
40
-
For available configuration settings, please refer to [Grafana Image Rendering documentation](https://grafana.com/docs/administration/image_rendering/).
47
+
You can run this plugin as a remote HTTP rendering service. In this setup, Grafana renders an image by making an HTTP request to the remote rendering service, which in turn renders the image and returns it back in the HTTP response to Grafana.
41
48
42
-
## Remote Rendering Using Docker
49
+
You can run the remote HTTP rendering service using Docker or as a standalone Node.js application.
43
50
44
-
Instead of installing and running the image renderer as a plugin, you can run it as a remote image rendering service using Docker. Read more about [remote rendering using Docker](https://github.com/grafana/grafana-image-renderer/blob/master/docs/remote_rendering_using_docker.md).
51
+
### Run in Docker
45
52
46
-
## Troubleshooting
53
+
Grafana Docker images are published at [Docker Hub](https://hub.docker.com/r/grafana/grafana-image-renderer).
54
+
55
+
The following example shows how you can run Grafana and the remote HTTP rendering service in two separate Docker containers using Docker Compose.
56
+
57
+
1. Create a `docker-compose.yml` with the following content:
The following example describes how to build and run the remote HTTP rendering service as a standalone Node.js application and configure Grafana appropriately.
86
+
87
+
1. Clone the [Grafana image renderer plugin](https://grafana.com/grafana/plugins/grafana-image-renderer) Git repository.
For available configuration settings, please refer to [Grafana Image Rendering documentation](https://grafana.com/docs/grafana/latest/image-rendering/#configuration).
114
+
115
+
## Troubleshooting
52
116
53
-
See [docs](https://github.com/grafana/grafana-image-renderer/blob/master/docs/index.md).
0 commit comments