Skip to content

Commit 1be063e

Browse files
vplauzonLeaShallev
andauthored
Update data-explorer/ingest-data-overview.md
Co-authored-by: Lea Shallev <[email protected]>
1 parent 7be4c4b commit 1be063e

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

data-explorer/ingest-data-overview.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,8 @@ Continuous data ingestion involves setting up an ingestion pipeline with either
5050
> For most scenarios, we recommend using queued ingestion as it is the more performant option.
5151
5252
> [!NOTE]
53-
> Queued ingestion queues data reliably but will be data is dropped after 7 days. Ensure your cluster has enough capacity to ingest data within 7 days.
53+
> Queued ingestion ensures reliable data buffering for up to 7 days. However, if the cluster lacks sufficient capacity to complete ingestion within this retention window, data will be dropped once the 7-day limit is exceeded.
54+
To avoid data loss and ingestion delays, please ensure your cluster has enough resources to process the queued data within the 7-day period.
5455

5556
There are multiple ways to configure continuous data ingestion. Use the following decision tree to determine the most suitable option for your use case:
5657

0 commit comments

Comments
 (0)