Plugin usage unclear according to docs
See original GitHub issueWhat would you like to be added:
Clear explanation what purpose this plugin fulfills and where it differs from the integrated Share -> Direct link rendered image functionality.
Why is this needed:
Docs state that:
Grafana supports automatic rendering of panels and dashboards as PNG images.
It seems that this functionality already exists as View -> Share -> Direct link rendered image.
Additionally, docs also points (or redirects) to https://grafana.com/docs/grafana/latest/administration/image_rendering/%7B%7B%20%3C%20relref%20%22/installation/docker/#build-with-grafana-image-renderer-plugin-pre-installed"%20>%20}} which doesn’t exist.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:5 (3 by maintainers)
Top Results From Across the Web
[BUG] Gradle Plugin - configOptions unclear / inconsistent
The gradle plugin offers some configuration option. But it's not clear what has to go where. The docs have an example:.
Read more >Systems Manager Command document plugin reference
This reference describes the plugins that you can specify in an AWS Systems Manager (SSM) Command type document. These plugins can't be used...
Read more >Using the Gatsby Image plugin
The Gatsby Image plugin handles the hard parts of producing images in ... For full documentation on all configuration options, see the reference...
Read more >Confused about useBuiltIns option of @babel/preset-env ...
1) Do I need to use that useBuiltIns: "entry" option? Yes, according to babel docs: "This option enables a new plugin that replaces...
Read more >Smartcrawl SEO Plugin Usage Documentation - WPMU Dev
If that works, it assumes that pretty permalinks are not working. You need to manually include some rewrite rules to your server's configuration...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@andig the reason is PhantomJS (which is pre-packaged with Grafana currently) is a dead project and not really a proper browser and is not something we want to continue build upon moving forward. Plugin/remote rendering service uses headless chrome.
That’s why we deprecated PhantomJS in Grafana v6.4, see release notes and changelog
For Grafana v7.0 we plan to remove PhantomJS (https://github.com/grafana/grafana/issues/13802)
I just migrated it here