Reporting error Request-URI Too Long #27728
Comments
|
Hello, I have just generated a report with 11 visualizations on my dashboard. Which browser and operating system are you using? Have you tried in different browsers? Cheers |
sebelga
added
the
Team:Visualizations
|
Pinging @elastic/kibana-app |
sebelga
added
the
(Deprecated) Feature:Reporting
|
I checked in Chrome, Opera and IE. Here is example on request that works fine (size 2327 bytes): and here is one of those failing (size 10200 bytes): |
|
I created a support case (#00239155) for Elastic on v6.3 on June 5th, 2018 regarding this. My problem description: "reason": "Watch[inlined] reporting[sample_report.pdf] Error response when trying to trigger reporting generation host[xxx], port[xxx] method[POST], path[/api/reporting/generate/printablePdf], status[414]" Throwing error code 414 seems to suggest that generation url is too long to handle. PDF reports for dashboard resulting in this watcher error can be manually generated from reporting menu, but I need also to include these in automatic email distribution. I have successfully generated PDF report sent by email for a dashboards with a generation url having a lenght of 5320 characters, but not for a length of 6800. Questions:
Support answer: |
|
Any progress on this issue? We are facing the same problem, i cannot create reports even using the web interface. Always Request-URI too long. |
|
I am currently facing this problem on Kibana 6.5.4 . |
|
6.7 has the same problem. CSV reports from discovery always fail, even with very small searched (less than 300 docs). |
|
Hello @Sjaak01 , this problem is not related to the amount of data to be processed, but on the length of the URL (probably linked to the number of filters applied on the data). |
|
Why Kibana is not using the short url "goto/94114215c4519bb135aed1b824e9dba7" to generate PDF ? |
timroes
added
Team:Stack Services
and removed
Team:Visualizations
|
Hi, this limitation seems mostly around how many panels can be on a dashboard used for Reporting. The Reporting POST URL contains data about Kibana's global state (such as query bar, filters, time pickers, etc) as well as the data about the dashboard saved object. If it was only the short URL used to generate Reports, we would lack the global state information. A data payload that has a combination of different sources seems like the best option: we can read all the dashboard saved object data from the Saved Object service. Unfortunately, that's not how Reporting works today. For now, the workaround is to create smaller dashboard PDFs. As @symstopje commented, looks like a URL for a dashboard with 8 panels works, but the same for a dashboard with 40 panels doesn't work. |
|
This issue is still present in 7.2. I don't consider creating smaller dashboards a valid workaround. In many cases that means you might miss out on important data and it is additional work. Taking a screenshot would be quicker. IMHO large amounts of visualizations should have been a consideration during development. |
|
@tsullivan I don't know if it is relevant but : or Why not use the short url to redirect to the long url for pdf generation locally? |
|
Hi, when I wrote We would have the global information in a short URL. It takes a snapshot of the browser state the same way that the Reporting POST URL does. Short URL and Reporting Generation URL seem similar in responsibility, but they're completely separate in functionality. With Security enabled, Kibana users are only able to create a short URL if they have write permission to Making short URLs and making reports don't really go hand-in-hand with the other in today's Kibana code. But, it's definitely something that needs to be pursued. I'm reading out to @elastic/kibana-app to see how we can align our goals. |
bmcconaghy
added
Team:ResponseOps
bmcconaghy
added
Team:Reporting Services
and removed
Team:ResponseOps
|
Pinging @elastic/kibana-reporting-services (Team:Reporting Services) |
|
Fixed in #45603 |
sophiec20
added
Feature:Reporting:Framework
Kibana version:
6.5.2 to 6.5.4
Elasticsearch version:
6.5.2 to 6.5.4
Server OS version:
Elastic cloud
Browser version:
Browser OS version:
Original install method (e.g. download page, yum, from source, etc.):
Describe the bug:
Generate pdf report in Kibana results in Reporting error Request-URI Too Long for medium size and big dashboars (message: Bad request for Kibana installed on own hosted server using yum)
Small reports work correctly
Steps to reproduce:
Expected behavior:
report processing startes
Screenshots (if relevant):
Errors in browser console (if relevant):
Provide logs and/or server output (if relevant):
Any additional context:
please see https://discuss.elastic.co/t/reporting-error-request-uri-too-long-reporting-error-bad-request/160050
The text was updated successfully, but these errors were encountered: