-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Rendering failed: Error: Failed to launch chrome" #159
Comments
Duplicate of #155. |
@aknuds1, so you say image renderer has external dependencies, right? As far as I remember I read something in the documentation hat there is one single binary which contains everything needed. Thanks for your help in advance!
|
You have to install Puppeteer's dependencies, as described here. |
Thanks Arve Below worked for me.
|
For me this helped on Ubuntu:
|
Tips: If you are using dokerfile, you need add |
@aknuds1 I think we should mention this dependencies issue here: https://grafana.com/grafana/plugins/grafana-image-renderer/ |
What happened:
Alert telegram messages don't have picture. Test message have at the telegram notification channel settings page (there is a button to send test alert message).
I set log level to debug and when alert telegram message has been sent I see below messages in the log. I have installed renderer plugin with this command then restarted grafana server:
grafana-cli plugins install grafana-image-renderer
What you expected to happen:
I expected to have a graph in my telegram message grafana sent to me via telegram.
How to reproduce it (as minimally and precisely as possible):
apt install -y software-properties-common
add-apt-repository "deb https://packages.grafana.com/oss/deb stable main"
wget -q -O - https://packages.grafana.com/gpg.key | apt-key add -
apt update
apt install grafana -y
grafana-cli plugins install grafana-image-renderer
/etc/init.d/grafana-server restart
Now set telegram plugin (bot ID), a graph and an alert for it.
Anything else we need to know?:
nothing
Environment:
The text was updated successfully, but these errors were encountered: