From d0ad9edce93def5168647d5a98f06a556345bba2 Mon Sep 17 00:00:00 2001 From: Nick Sanford Date: Thu, 14 Nov 2024 10:12:45 -0500 Subject: [PATCH] wip --- docs/services/data/_index.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/services/data/_index.md b/docs/services/data/_index.md index 0e83c474ea9..c74b9e2efe5 100644 --- a/docs/services/data/_index.md +++ b/docs/services/data/_index.md @@ -180,9 +180,9 @@ Failing to write to MongoDB doesn't affect capturing & syncing data to cloud sto {{< alert title="Caution" color="caution" >}} -- Capturing Directly to MongoDB may write data to MongoDB that later fails to be written to disk (and therefore never gets synced to app.viam.com). -- Capturing Directly to MongoDB does not retry failed writes to MongoDB. As a consequence, it is NOT guaranteed all data captured will be written to MongoDB. This can happen in cases such MongoDB being inaccessible to viam-server or writes timing out. -- Capturing Directly to MongoDB may reduce the maximum frequency that Data Capture can capture data due to the added latency of writing to MongoDB. If your usecase needs to support very high capture rates, this feature may not be appropriate. +- Capturing directly to MongoDB may write data to MongoDB that later fails to be written to disk (and therefore never gets synced to cloud stroage). +- Capturing directly to MongoDB does not retry failed writes to MongoDB. As a consequence, it is NOT guaranteed all data captured will be written to MongoDB. This can happen in cases such MongoDB being inaccessible to viam-server or writes timing out. +- Capturing directly to MongoDB may reduce the maximum frequency that Data Capture can capture data due to the added latency of writing to MongoDB. If your use case needs to support very high capture rates, this feature may not be appropriate. {{< /alert >}}