Skip to content
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

[Dashboard] Cannot complete generating a PDF or PNG report #116720

Closed
TinaHeiligers opened this issue Oct 28, 2021 · 7 comments
Closed

[Dashboard] Cannot complete generating a PDF or PNG report #116720

TinaHeiligers opened this issue Oct 28, 2021 · 7 comments
Labels
bug Fixes for quality problems that affect the customer experience (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead Feature:Dashboard Dashboard related features impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. loe:needs-research This issue requires some research before it can be worked on or estimated Team:Presentation Presentation Team for Dashboard, Input Controls, and Canvas

Comments

@TinaHeiligers
Copy link
Contributor

TinaHeiligers commented Oct 28, 2021

Kibana & Elasticsearch version:
7.16

Browser:
Safari Version 15.0 (16612.1.29.41.4, 16612)

Environment
Cloud (admin staging)

Describe the bug:
In Dashboards, there's an option to create a report that should complete and be downloadable from the Reporting app. This should also be the case now with the ability to generate reports from Dashboards that have unsaved changes.

When using Safari, the reporting job for PNG and PDF reports errors out when the a PNG or PDF report is generated from a Dashboard with unsaved changes.

Steps to reproduce:

  1. With Safari, Navigate to the Dashboard app
  2. Select an existing Dashboard or create a new one
  3. Edit the dashboard (if using an existing one) or add a visualization if creating a new Dashboard.
  4. Do not saved the changes/addition
  5. Generate a report (either PDF or PNG)
  6. Wait for a few minutes for the report to generate
  7. Navigate to the Reporting application
  8. Observe that the PNG/PDF report has errors.

Expected behavior:
The report should generate successfully.

Screenshots (if relevant):

reports_generated_from_DB

individual_report_issue

Safari_reporting_issue

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):
No warnings or errors observed.

@TinaHeiligers TinaHeiligers added bug Fixes for quality problems that affect the customer experience Feature:Dashboard Dashboard related features (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead loe:needs-research This issue requires some research before it can be worked on or estimated impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. labels Oct 28, 2021
@botelastic botelastic bot added the needs-team Issues missing a team label label Oct 28, 2021
@kibanamachine kibanamachine added the Team:Presentation Presentation Team for Dashboard, Input Controls, and Canvas label Oct 28, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-presentation (Team:Presentation)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Oct 28, 2021
@liza-mae
Copy link
Contributor

This appear to be a duplicate of: #106873 - The report not generating is possibly due to it being a large dashboard, can you confirm? Do all reports for a smaller dashboard also fail on Mac OSX or just this one?

Diagnostic fails is also known here: #106873 (comment) but has been fixed recently here: #116199

@TinaHeiligers
Copy link
Contributor Author

The dashboard isn't all that big but does span quite a lot of data. I confirmed the bug using a much smaller dataset powering the dashboards and a small dashboard from Kibana sample data too ("By Value DB" uses the Kibana logs sample data set).
Screen Shot 2021-10-29 at 08 19 26

@poffdeluxe
Copy link
Contributor

@TinaHeiligers does your cloud instance have 4GB of Memory? Reporting on cloud recommends around that much and it isn't the default https://www.elastic.co/guide/en/kibana/current/reporting-troubleshooting.html#reporting-troubleshooting-system-requirements

@TinaHeiligers
Copy link
Contributor Author

@poffdeluxe If 4GB isn't the default then I doubt the instance had that much allocated to it. Unfortunately, that specific deployment was auto-terminated so I can't check that one specifically.

@liza-mae
Copy link
Contributor

liza-mae commented Nov 15, 2021

The default on cloud is 1GB

@TinaHeiligers
Copy link
Contributor Author

TinaHeiligers commented Nov 16, 2021

The default on cloud is 1GB

I upgraded a different 7.16 deployment's Kibana to 4GB and generating the PNG report from an unsaved dashboard created from visualizations added by value works as expected.

Closing this issue as it isn't a bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead Feature:Dashboard Dashboard related features impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. loe:needs-research This issue requires some research before it can be worked on or estimated Team:Presentation Presentation Team for Dashboard, Input Controls, and Canvas
Projects
None yet
Development

No branches or pull requests

5 participants