mirror of
https://github.com/elastic/kibana.git
synced 2025-06-28 03:01:21 -04:00
c1e751d9ff
## Summary This PR offers small updates to documentation on: * Calling Kibana APIs to automate report generation * Using Elasticsearch APIs directly to export data
14 lines
No EOL
1.4 KiB
Text
14 lines
No EOL
1.4 KiB
Text
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.
|
|
|
|
For more information on using Elasticsearch APIs directly, 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. We recommend that you use an official Elastic language client: details for each programming language library that Elastic provides are in the https://www.elastic.co/guide/en/elasticsearch/client/index.html[{es} Client documentation].
|
|
|
|
<<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. |