-
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
Puppeteer: Set protocolTimeout #482
Comments
We are seeing strange performance problems generating PDFs. We have a generous global timeout set (10 minutes), but some of the panels are still failing randomly, and show an error in the produced PDF. The same panel may work fine on a subsequent attempt. There isn't any apparent patturn to the failures that we've been able to determine. This started in the latest version of Grafana Cloud at about the time of this issue. We are on currently on Grafana 10.3. Example: Thank you for your work on the renderer and gofpdf. |
Hi @johndunderhill does the issue persist, yet? |
I will check and get back to you.
John
…________________________________
From: Juan Cabanas ***@***.***>
Sent: Tuesday, December 17, 2024 11:16:24 AM
To: grafana/grafana-image-renderer ***@***.***>
Cc: John D. Underhill ***@***.***>; Mention ***@***.***>
Subject: Re: [grafana/grafana-image-renderer] Puppeteer: Set protocolTimeout (Issue #482)
Hi @johndunderhill does the issue persist, yet? We're making a big change in the report generation process under newPDFRendering and reportingUseRawTimeRange FF. We plan to enable them by default in G
[cid:inky-injection-inliner-6f42d488d348cfcd86bff9497caf9f6a]
External ***@***.******@***.***>)
Hi @johndunderhill<https://github.com/johndunderhill> does the issue persist, yet?
We're making a big change in the report generation process under newPDFRendering and reportingUseRawTimeRange FF. We plan to enable them by default in Grafana 11.5.
This allows creating the report by visiting the dashboard once, instead of visiting panel by panel and fixes many timeout issues.
—
Reply to this email directly, view it on GitHub<#482 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AGDRBW73NXOLCF3NSHMN2VL2GB2ARAVCNFSM6AAAAABTZDKRUGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBZGM4TQOJTGM>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
In "recent" version of Puppeteer, a new timeout had been added and ignore the one we can send to the image renderer. We should configure it either with the value configured in the image renderer settings (if possible) or with 0 (no timeout).
The text was updated successfully, but these errors were encountered: