search

IzakMarais / reporter

Service that generates a PDF report from a Grafana dashboard
Apache License 2.0
958 stars 308 forks source link

Error obtaining render for panel #180

Open madmax01 opened 4 years ago

madmax01 commented 4 years ago

Hi ,

i installed latest grafana and reporter.

i use this dashboard as an test:

https://grafana.com/grafana/dashboards/8168

if i just leave VM = ALL then it works.

but once i just want to report 1 VM VM = XXX

then i get errors

Error obtaining render for panel. and task running endless.

amirmalka commented 4 years ago

Same issue here, using Grafana 6.5.1 and latest reporter version. From Grafana Logs:

t=2019-12-31T08:14:02+0000 lvl=info msg="Rendering timed out" logger=rendering t=2019-12-31T08:14:02+0000 lvl=eror msg="Timeout error. You can set timeout in seconds with &timeout url parameter" logger=context userId=0 orgId=1 uname= error="Timeout error. You can set timeout in seconds with &timeout url parameter" t=2019-12-31T08:14:02+0000 lvl=eror msg="Request Completed" logger=context userId=0 orgId=1 uname= method=GET path=/render/d-solo/vigVSrrizm/_ status=500 remote_addr=172.18.0.1 time_ms=62083 size=1782 referer=

IzakMarais commented 4 years ago

Seems like it might be a grafana bug. You can call that get endpoint directly using curl to test independently from the reporter.

madmax01 commented 4 years ago

just a workaround.

once doing the filter > the whole dashboard need to be saved. without saving Dashboard = seems not working.

bit Strange needing to save all time the dashboard once changing just the View

IzakMarais commented 4 years ago

Any progress in reproducing this independently of the reporter?

moon-hawk commented 4 years ago

I have also this issue in Grafana Version 6.5.2 In another installation with Grafana Version 6.3.2 everything is fine.

Is it possible its connected to this?

Deprecation notes PhantomJS

PhantomJS, which is used for rendering images of dashboards and panels, is deprecated and will be removed in a future Grafana release. A deprecation warning will from now on be logged when Grafana starts up if PhantomJS is in use.

Please consider migrating from PhantomJS to the Grafana Image Renderer plugin.

See Version 6.4.0-beta1 in https://github.com/grafana/grafana/blob/master/CHANGELOG.md

moon-hawk commented 4 years ago

But not sure if the message befor is relevant. I made the following observation: When i go throught the logs it shows a call to: "GRAFANA_URL/render/d-solo/BORD_ID/..." If i call this directly i get the error. When i run the this without "/render", i get an html document of one of the panels.

So it looks for me like the image rendering part is the source of the problem...

mankuuuuu commented 3 years ago

Check if all the depended libraries are installed for image renderer working fine for me. https://grafana.com/docs/grafana/latest/administration/image_rendering/#troubleshoot-image-rendering

moon-hawk commented 3 years ago

@mankuuuuu thank you for that. We have

after tests i can confirm that grafana-reporter works with grafana > 6.4 and grafana-image-renderer plugin