-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Option to break "preserve layout" reports into multiple pages #36606
Comments
Pinging @elastic/kibana-app |
If there was an element on the dashboard that could group other elements into a square, it may be possible to have the headless browser capture screenshots of each group. Then each group could have its own layout of visualizations, and one group can be captured per page. |
I found some experiments from @stacey-gammon in this direction: #16919
Dashboard Panel Group == single page of a dashboard PDF? |
Depending on how far someone would want to go for their goal here, one workaround would be to use Canvas for the presentation of data to report on. We're still working on performance improvements with Canvas + Reporting, but when things go smoothly, the PDF features each page of the worksheet separately. |
NOTE: Issues like this will need to go back to the Kibana App team. The dashboard layouts are modes of the App integration with the Reporting service. The Reporting team will not be able to drive improvements on how the integration is done, but we can support adding any additional hooks that would help here. |
Pinging @elastic/kibana-reporting-services (Team:Reporting Services) |
Pinging @elastic/kibana-app-services (Team:AppServices) |
Closing this as inactive. There have been no further user requests for this. |
Some users would like to have the ability to use the Preserve Layout when generating a PDF report and have it split out into multiple pages. This could be based on the page size or use a particular visualization in the Dashboard to create a sort of "Page break".
The text was updated successfully, but these errors were encountered: