-
Notifications
You must be signed in to change notification settings - Fork 152
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
This plugin ignores config. How change settings? #342
Comments
Hi! The To set the width, height and scale when rendering a panel, you should set this information as query parameters in this rendering request:
|
Hi! |
can I change the default values of width and height ? |
Hi @Codecaver,
Seems it is supported, but only when running the renderer as gRPC plugin, through environment variables: I'm going to create an issue to evaluate if that should be supported when running the renderer as standalone application, as well. Thanks! |
Closing this in favor of #392 |
What happened:
Hi! I am trying to follow the instructions: https://grafana.com/docs/grafana/next/image-rendering/
In my case, this is the plugin mode.
Trying to change quality of picture, I made the following changes to my config file (
/etc/grafana/grafana.ini
):even tried adding
--window-size=1280x640
torendering_args
...but every time I see in the log:
logger=rendering renderer=plugin t=2022-04-02T02:04:31.03+0300 lvl=dbug msg="Calling renderer plugin" req="url:\"http://localhost:3000/d-solo/Z_ov_As7k/all-servers-stats?orgId=1&panelId=8&render=1\" width:1000 height:500 deviceScaleFactor:1 filePath:\"/var/lib/grafana/png/HpySZFwXdlfyHA4ZcP8S.png\" renderKey:\"ceic3WlvNO7Dsv3lZYht3mStXIJ269hZ\" domain:\"localhost\" timeout:15"
As I see: the plugin receives an image of 1000x500, with scale factor = 1. The main question is: why?
After changes
grafana.ini
I restartedgrafana-server
.What you expected to happen:
I expect the plugin to react to changing settings)
How to reproduce it (as minimally and precisely as possible):
Just edit config file...
Environment:
The text was updated successfully, but these errors were encountered: