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

[Docs] Clarifying CSV limitations (#175208)

Browse source 
## Summary 

Adding CSV limitations section
This commit is contained in:
Anton Dosov 2024-01-25 17:04:15 +01:00 • committed by GitHub
parent 907eb90315
commit 2ea91b14e7
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 17 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

8
docs/user/reporting/index.asciidoc
View file

@ -15,7 +15,7 @@ You access the options from the *Share* menu in the toolbar. The sharing options
* *PNG Reports* — Generate and download PNG files of dashboards and visualizations. PNG reports are a link:https://www.elastic.co/subscriptions[subscription feature].
* *CSV Reports* — Generate and download CSV files of saved searches.
* *CSV Reports* &mdash; Generate and download CSV files of saved searches. <<csv-limitations,Certain limitations apply>>.
* *CSV Download* &mdash; Generate and download CSV files of *Lens* visualizations.
@ -72,6 +72,12 @@ NOTE: Reports are stored in {es} and managed by the `kibana-reporting` {ilm}
more about {ilm-init} policies, refer to the {es}
{ref}/index-lifecycle-management.html[{ilm-init} documentation].
[float]
[[csv-limitations]]
=== CSV reports limitations
include::reporting-csv-limitations.asciidoc[]
[float]
[[share-a-direct-link]]
== Share direct links

10
docs/user/reporting/reporting-csv-limitations.asciidoc Normal file
View file

@ -0,0 +1,10 @@
We recommend using CSV reports to export moderate amounts of data only. The feature enables analysis of data in external tools, but it is not intended for bulk export or to backup Elasticsearch data. Report timeout and incomplete data issues are likely if you are exporting data where:
- More than 250 MB of data is being exported
- Data is stored on slow storage tiers
- Any shard needed for the search is unavailable
- Network latency between nodes is high
- Cross-cluster search is used
- ES|QL is used and result row count exceeds the limits of ES|QL queries
To work around the limitations, use filters to create multiple smaller reports, or extract the data you need directly with the Elasticsearch APIs. See {ref}/scroll-api.html[Scroll API], {ref}/point-in-time-api.html[Point in time API], {ref}/esql-rest.html[ES|QL] or {ref}/sql-rest-format.html#_csv[SQL] with CSV response data format. <<reporting-settings-kb, Reporting parameters>> can be adjusted to overcome some of these limiting scenarios. Results are dependent on data size, availability, and latency factors and are not guaranteed.