github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-24 09:48:58 -04:00
Code Issues Projects Releases Packages Wiki Activity

[Reporting Docs for inspecting the query used for CSV export (#207001)

Browse source 
Closes https://github.com/elastic/kibana/issues/191768

---------

Co-authored-by: wajihaparvez <wajiha.parvez@elastic.co>
This commit is contained in:
Tim Sullivan 2025-01-17 01:48:15 -07:00 • committed by GitHub
parent 8de55a4d96
commit a514c26d38
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 15 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

15
docs/user/reporting/reporting-csv-troubleshooting.asciidoc
View file

@ -69,6 +69,21 @@ Such changes aren't guaranteed to solve the issue, but give the functionality a
chance of working in this use case.
Unfortunately, lowering the scroll size will require more requests to Elasticsearch during export, which adds more time overhead, which could unintentionally create more instances of auth token expiration errors.
[float]
[[reporting-troubleshooting-inspect-query-used-for-export]]
=== Inspecting the query used for CSV export
The listing of reports in *Stack Management > Reporting* allows you to inspect the query used for CSV export. It can be helpful to see the raw responses
from Elasticsearch, or determine if there are performance improvements to be gained by changing the way you query the data.
1. Go to **Stack Management > Reporting** and click the info icon next to a report.
2. In the footer of the report flyout, click **Actions**.
3. Click **Inspect query in Console** in the **Actions** menu.
4. This will open the *Console* application, pre-filled with the queries used to generate the CSV export.
[role="screenshot"]
image::https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt4758e67aaec715d9/67897d0be92e090a6dc626a8/inspect-query-from-csv-export.gif[Inspect the query used for CSV export]
[float]
[[reporting-troubleshooting-csv-token-expired]]
=== Token expiration