20 first lines complete check on reporting folder, unedited

Author: florent-leborgne

explore-analyze/report-and-share/automating-report-generation.md

@@ -1,4 +1,5 @@
 ---
+description: Generate reports automatically using {{watcher}}, scripts, or scheduled tasks. Configure recurring exports and share PDF, PNG, or CSV reports by email.
 mapped_pages:
   - https://www.elastic.co/guide/en/kibana/current/automating-report-generation.html
 applies_to:
@@ -10,11 +11,23 @@ products:
 
 # Automatically generate reports [automating-report-generation]
 
-To automatically generate PDF and CSV reports, generate a POST URL, then submit an HTTP `POST` request using {{watcher}} or a script. In {{stack}} 9.1 and Serverless, you can use {{kib}} to generate reports on a recurring schedule and share them with a list of emails that you specify.
+Automate report generation to share dashboards, visualizations, and data exports on a regular schedule. You can use {{watcher}} or scripts to trigger report generation through a POST URL, or set up recurring schedules directly in {{kib}} to generate and email reports automatically.
+
+Three approaches are available for automating reports:
+
+* **{{watcher}}**: Configure watches that generate and email reports based on schedules or conditions
+* **Scripts**: Use HTTP POST requests to programmatically generate reports on demand
+* **Scheduled exports**: {applies_to}`stack: preview 9.1, serverless: preview` Set up recurring tasks in {{kib}} that automatically generate and share reports by email
+
+**Prerequisites:**
+
+* Appropriate {{kib}} privileges to create reports
+* {applies_to}`stack: ga` API key or user credentials with reporting permissions
+* {applies_to}`stack: preview 9.1, serverless: preview` For scheduled email sharing, a configured email connector
 
 :::{note}
 :applies_to: {stack: ga, serverless: unavailable}
-API keys are used to authenticate requests to generate reports. If you have a cross-cluster search environment and want to generate reports from remote clusters, you must have the appropriate cluster and index privileges on the remote cluster and local cluster. For example, if requests are authenticated with an API key, the API key requires certain privileges on the local cluster that contains the leader index, instead of the remote. For more information and examples, refer to [Configure roles and users for remote clusters](../../deploy-manage/remote-clusters/remote-clusters-cert.md#remote-clusters-privileges-cert).
+{{api-keys-app}} are used to authenticate requests to generate reports. If you have a {{ccs}} environment and want to generate reports from remote clusters, you must have the appropriate cluster and index privileges on the remote cluster and local cluster. For example, if requests are authenticated with an API key, the API key requires certain privileges on the local cluster that contains the leader index, instead of the remote. For more information and examples, refer to [Configure roles and users for remote clusters](../../deploy-manage/remote-clusters/remote-clusters-cert.md#remote-clusters-privileges-cert).
 :::
 
 ## Create a POST URL [create-a-post-url]

explore-analyze/report-and-share/reporting-troubleshooting-csv.md

@@ -1,4 +1,5 @@
 ---
+description: Troubleshoot common CSV export issues including timeouts, socket errors, token expiration, and scroll API configuration.
 navigation_title: CSV
 mapped_pages:
   - https://www.elastic.co/guide/en/kibana/current/reporting-troubleshooting-csv.html
@@ -13,31 +14,34 @@ products:
 
 # CSV [reporting-troubleshooting-csv]
 
+CSV export in {{kib}} queries {{es}} and formats the results as downloadable CSV files. While this works well for moderate data exports, issues can occur with large datasets, slow storage, network latency, or authentication timeouts. This page helps you diagnose and resolve common CSV export problems.
+
+Common issues include:
+
+* Report timeouts when exporting more than 250 MB of data
+* Incomplete data when shards are unavailable or using {{ccs}}
+* Socket hangup errors during long-running exports
+* Token expiration for SAML-authenticated deployments
+
+For general troubleshooting guidance, refer to [Troubleshooting](reporting-troubleshooting.md).
 
 ::::{note}
-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:
+CSV export is designed for moderate data amounts only. It enables data analysis in external tools but is not intended for bulk export or {{es}} backups. Report timeout and incomplete data issues are likely when 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.
+* {{ccs}} is used
+* {{esql}} is used and result row count exceeds the limits of {{esql}} queries
 
-For more information on using Elasticsearch APIs directly, see [Scroll API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-scroll), [Point in time API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-open-point-in-time), [ES|QL](elasticsearch://reference/query-languages/esql/esql-rest.md) or [SQL](elasticsearch://reference/query-languages/sql/sql-rest-format.md#_csv) 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 [{{es}} Client documentation](/reference/elasticsearch-clients/index.md).
+To work around these limitations, use filters to create multiple smaller reports, or extract data directly with {{es}} APIs. For information on using {{es}} APIs directly, refer to [Scroll API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-scroll), [Point in time API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-open-point-in-time), [{{esql}}](elasticsearch://reference/query-languages/esql/esql-rest.md), or [SQL](elasticsearch://reference/query-languages/sql/sql-rest-format.md#_csv) with CSV response data format. Consider using an official {{es}} client: refer to [{{es}} Client documentation](/reference/elasticsearch-clients/index.md).
 
-[Reporting parameters](kibana://reference/configuration-reference/reporting-settings.md) can be adjusted to overcome some of these limiting scenarios. Results are dependent on data size, availability, and latency factors and are not guaranteed.
+You can adjust [Reporting parameters](kibana://reference/configuration-reference/reporting-settings.md) to overcome some limiting scenarios. Results depend on data size, availability, and latency factors and are not guaranteed.
 
 ::::
 
 
-The CSV export feature in Kibana makes queries to Elasticsearch and formats the results into CSV. This feature offers a solution that attempts to provide the most benefit to the most use cases. However, things could go wrong during export. Elasticsearch can stop responding, repeated querying can take so long that authentication tokens can time out, and the format of exported data can be too complex for spreadsheet applications to handle. Such situations are outside of the control of Kibana. If the use case becomes complex enough, it’s recommended that you create scripts that query Elasticsearch directly, using a scripting language like Python and the public {{es}} APIs.
-
-For advice about common problems, refer to [Troubleshooting](reporting-troubleshooting.md).
-
-
 ## Configuring CSV export to use the scroll API [reporting-troubleshooting-csv-configure-scan-api]
 
 The Kibana CSV export feature collects all of the data from Elasticsearch by using multiple requests to page over all of the documents. Internally, the feature uses the [Point in time API and `search_after` parameters in the queries](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-open-point-in-time) to do so. There are some limitations related to the point in time API:

explore-analyze/report-and-share/reporting-troubleshooting-pdf.md

@@ -1,4 +1,5 @@
 ---
+description: Troubleshoot PDF and PNG export issues including browser dependencies, sandbox requirements, font rendering, connection errors, and system requirements.
 navigation_title: PDF/PNG
 mapped_pages:
   - https://www.elastic.co/guide/en/kibana/current/reporting-troubleshooting-pdf.html
@@ -13,16 +14,26 @@ products:
 
 # PDF/PNG [reporting-troubleshooting-pdf]
 
+PDF and PNG reporting in {{kib}} uses a headless Chromium browser to capture screenshots of dashboards and visualizations. Issues can occur due to missing system dependencies, sandbox restrictions, font problems, or resource constraints. This page helps you diagnose and resolve common PDF and PNG export problems.
 
-::::{note}
-We recommend using PNG/PDF reports to export moderate amounts of data only. The feature enables a high-level export capability, but it’s not intended for bulk export. If you need to export several pages of image data, consider using multiple report jobs to export a small number of pages at a time. If the screenshot of exported dashboard contains a large number of pixels, consider splitting the large dashboard into smaller artifacts to use less memory and CPU resources.
+Common issues include:
 
-For the most reliable configuration of PDF/PNG {{report-features}}, consider installing {{kib}} using [Docker](../../deploy-manage/deploy/self-managed/install-kibana-with-docker.md) or using [Elastic Cloud](https://cloud.elastic.co).
+* Missing Network Security Service (NSS) libraries
+* Chromium sandbox requirements and user namespace restrictions
+* Text rendering incorrectly due to missing fonts
+* Connection refused errors with server host settings
+* Memory limitations causing page crashes
 
-::::
+**Technical summary**: Use the built-in reporting diagnostics tool at **{{reports-app}} > Run reporting diagnostics** to identify common configuration issues. For Docker or {{ecloud}} deployments, most dependencies are preconfigured.
+
+For general troubleshooting guidance, refer to [Troubleshooting](reporting-troubleshooting.md).
 
+::::{note}
+PDF and PNG reports work best with moderate amounts of visual data. The feature provides high-level export capability but is not intended for bulk export. If you need to export several pages of image data, use multiple report jobs to export a small number of pages at a time. If exported dashboard screenshots contain a large number of pixels, split large dashboards into smaller artifacts to reduce memory and CPU usage.
+
+For the most reliable configuration of PDF/PNG {{report-features}}, install {{kib}} using [Docker](../../deploy-manage/deploy/self-managed/install-kibana-with-docker.md) or use [{{ecloud}}](https://cloud.elastic.co).
 
-For more advice about common problems, refer to [Troubleshooting](reporting-troubleshooting.md).
+::::
 
 
 ## Reporting diagnostics [reporting-diagnostics]

explore-analyze/report-and-share/reporting-troubleshooting.md

@@ -1,4 +1,5 @@
 ---
+description: Diagnose and resolve common reporting errors including version conflicts, max attempts reached, and timeout issues. Enable verbose logging for troubleshooting.
 navigation_title: Troubleshoot reporting
 mapped_pages:
   - https://www.elastic.co/guide/en/kibana/current/reporting-troubleshooting.html
@@ -13,10 +14,15 @@ products:
 
 # Troubleshoot report errors and logs in {{kib}} [reporting-troubleshooting]
 
+{{report-features}} in {{kib}} are designed for simple data exports and visualizations, not bulk data export or large-scale operations. When you encounter issues generating reports, understanding common error messages and enabling verbose logging can help you diagnose and resolve problems quickly.
 
-Kibana excels as a data visualization tool. The {{report-features}} exist to export data as simple reports, however Kibana is not a data export tool. To export data at a large scale, there are better ways and better architectures for exporting data at scale from Elasticsearch.
+Common issues include:
 
-If you have trouble creating simple reports, there are some general solutions to common problems you might encounter while using {{report-features}}. For tips related to specific types of reports, refer to [CSV](reporting-troubleshooting-csv.md) and [PDF/PNG](reporting-troubleshooting-pdf.md).
+* Version conflict exceptions in clustered environments
+* "Max attempts reached" errors due to timeouts or configuration issues
+* Report failures with large datasets or complex visualizations
+
+For issues specific to report formats, refer to [CSV troubleshooting](reporting-troubleshooting-csv.md) and [PDF/PNG troubleshooting](reporting-troubleshooting-pdf.md).
 
 
 ## Error messages [reporting-troubleshooting-error-messages]