Skip to content

Repo sync for protected branch #2640

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
learn-build-service-prod merged 5 commits into from
Jun 3, 2025
Merged

Repo sync for protected branch #2640

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
7be4c4b
Add warning
vplauzon May 29, 2025
1be063e
Update data-explorer/ingest-data-overview.md
vplauzon Jun 3, 2025
bc0a792
Merge pull request #6885 from vplauzon/vpl/add-warning
denrea Jun 3, 2025
01df348
Merge pull request #6897 from MicrosoftDocs/main
Taojunshen Jun 3, 2025
dd06dd6
Merging changes synced from https://github.com/MicrosoftDocs/dataexpl…
Jun 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion data-explorer/ingest-data-overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -49,6 +49,10 @@ 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 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:

:::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.":::
Expand Down