From 7be4c4bffbdbe20a388b6de587925abbd8294631 Mon Sep 17 00:00:00 2001 From: vplauzon Date: Thu, 29 May 2025 11:55:50 -0400 Subject: [PATCH 1/2] Add warning --- data-explorer/ingest-data-overview.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/data-explorer/ingest-data-overview.md b/data-explorer/ingest-data-overview.md index 40629353c8..c35480473a 100644 --- a/data-explorer/ingest-data-overview.md +++ b/data-explorer/ingest-data-overview.md @@ -3,7 +3,7 @@ title: Azure Data Explorer data ingestion overview description: Learn about the different ways you can ingest (load) data in Azure Data Explorer ms.reviewer: akshay.dixit ms.topic: conceptual -ms.date: 04/07/2025 +ms.date: 05/29/2025 --- # Azure Data Explorer data ingestion overview @@ -49,6 +49,9 @@ Continuous data ingestion involves setting up an ingestion pipeline with either > [!NOTE] > For most scenarios, we recommend using queued ingestion as it is the more performant option. +> [!NOTE] +> 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. + There are multiple ways to configure continuous data ingestion. Use the following decision tree to determine the most suitable option for your use case: :::image type="complex" border="false" source="media/ingest-data-overview/continuous-ingestion.png" lightbox="media/ingest-data-overview/continuous-ingestion.png" alt-text="Diagram of decision tree for continuous ingestion."::: From 1be063eec447e3f766ec5c0a5a4bfea394404f22 Mon Sep 17 00:00:00 2001 From: Vincent-Philippe Lauzon Date: Tue, 3 Jun 2025 13:05:42 -0400 Subject: [PATCH 2/2] Update data-explorer/ingest-data-overview.md Co-authored-by: Lea Shallev --- data-explorer/ingest-data-overview.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/data-explorer/ingest-data-overview.md b/data-explorer/ingest-data-overview.md index c35480473a..71dcd7f70d 100644 --- a/data-explorer/ingest-data-overview.md +++ b/data-explorer/ingest-data-overview.md @@ -50,7 +50,8 @@ Continuous data ingestion involves setting up an ingestion pipeline with either > For most scenarios, we recommend using queued ingestion as it is the more performant option. > [!NOTE] -> 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. +> 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. +To avoid data loss and ingestion delays, please ensure your cluster has enough resources to process the queued data within the 7-day period. There are multiple ways to configure continuous data ingestion. Use the following decision tree to determine the most suitable option for your use case: