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

[Reporting] report generation timeout when visualisation has error #50084

Closed
nerophon opened this issue Nov 7, 2019 · 5 comments
Closed

[Reporting] report generation timeout when visualisation has error #50084

nerophon opened this issue Nov 7, 2019 · 5 comments
Labels
bug Fixes for quality problems that affect the customer experience (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead

Comments

@nerophon
Copy link
Contributor

nerophon commented Nov 7, 2019

Kibana version: 7.3.2

Elasticsearch version: 7.3.2

Server OS version: Red Hat Enterprise Linux Server release 7.7 (Maipo)

Browser version: Chrome Version 76.0.3809.87 (Official version) (64-bit)

Browser OS version: windows 7

Original install method (e.g. download page, yum, from source, etc.): Yum install

Describe the bug:
If dashboard contains a visualization, that contains an error then Report generation will not work. It will just time out. It will not like the online dashboard view , display an error message about the problem.

Steps to reproduce:

  1. create a dashboard with a visualisation that has an error which prints to the screen (see below example screenshot)
  2. attempt to generate a report from the dashboard

Expected behavior: report generation should fail at once, possibly printing the error

Screenshots (if relevant):

@nerophon nerophon added bug Fixes for quality problems that affect the customer experience (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead labels Nov 7, 2019
@nerophon
Copy link
Contributor Author

nerophon commented Nov 7, 2019

2019-11-07 09_25_13-bd-custom-idps - Kibana – Google Chrome

@tsullivan
Copy link
Member

Hi, can you include some logs on this that show a failure reason?

Is this issue similar: #52350

@tsullivan
Copy link
Member

ping @elastic/kibana-stack-services

@bmcconaghy bmcconaghy added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) and removed Team:Stack Services labels Dec 12, 2019
@bmcconaghy bmcconaghy added Team:Reporting Services and removed Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Dec 20, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-reporting-services (Team:Reporting Services)

@tsullivan
Copy link
Member

Fixed in #58683 and released in Kibana 7.7.0

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
Projects
None yet
Development

No branches or pull requests

4 participants