-
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
Reporting: Generating report for large dashboard fails #106873
Comments
Pinging @elastic/kibana-app-services (Team:AppServices) |
@liza-mae, The error @tsullivan, I've addressed the error in the Reporting Diagnostics in #107282. Should we create a separate issue for the regression because the error is not related to the large dashboards? |
I think it's fine to get that fix in without opening a separate issue. |
@liza-mae hopefully when the diagnostic issue is fixed, you'll be able to see why reporting is not working on this Linux instance. |
@liza-mae any update on this? |
@tsullivan The diagnostic errors are now fixed and it gives me proper diagnostic error messages. The diagnostic states to increase |
Logs
|
@liza-mae the solution is to use a smaller dashboard that works for the test instance. The diagnostic tool errors look like a separate issue, unrelated to generating report for a large dashboard. |
Same issue in 7.13: #102006 |
duplicate of #100461 |
Kibana version: 8.0.0-alpha1
Elasticsearch version: 8.0.0-alpha1
Server OS version: Linux
Browser version: Chrome
Browser OS version: Latest
Original install method (e.g. download page, yum, from source, etc.):
Staging
Description of the problem including expected versus actual behavior:
Generate large dashboard report should work, however it returns error unexpected token E in JSON at position 0
Steps to reproduce:
Unable to fetch report content Unexpected token E in JSON at position 0
NOTE: The reporting diagnostic also failed with an error can't read property http of undefined.
I have seen reporting fail on large dashboards before, but the errors showing are different here, so not sure if it is the same root cause.
The text was updated successfully, but these errors were encountered: