You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/data-ai/capture-data/advanced/advanced-data-capture-sync.md
+58-5
Original file line number
Diff line number
Diff line change
@@ -579,24 +579,27 @@ The following sample configuration captures data from a sensor at 0.5 Hz.
579
579
580
580
{{% /expand%}}
581
581
582
-
### Capture directly to local MongoDB
582
+
### Capture directly to your own MongoDB cluster
583
583
584
584
You can configure direct capture of tabular data to a MongoDB instance alongside disk storage on your edge device.
585
585
This can be useful for powering real-time dashboards before data is synced from the edge to the cloud.
586
+
The MongoDB instance can be a locally running instance or a cluster in the cloud.
586
587
587
588
Configure using the `mongo_capture_config` attributes in your data manager service.
589
+
You can configure data sync to a MongoDB instance separately from data sync to the Viam Cloud.
588
590
589
-
Here is a sample configuration that will capture fake sensor readings both to the configured MongoDB URI as well as to the `~/.viam/capture` directory on disk:
591
+
{{< expand "Click to view sample configuration with MongoDB data store." >}}
590
592
591
-
{{< expand "Click to view configuration" >}}
593
+
This sample configuration captures fake sensor readings both to the configured MongoDB URI as well as to the `~/.viam/capture` directory on disk.
594
+
It does not sync the data to the Viam Cloud.
592
595
593
596
```json
594
597
{
595
598
"components": [
596
599
{
597
600
"name": "sensor-1",
598
601
"api": "rdk:component:sensor",
599
-
"model": "fake",
602
+
"model": "rdk:builtin:fake",
600
603
"attributes": {},
601
604
"service_configs": [
602
605
{
@@ -618,7 +621,6 @@ Here is a sample configuration that will capture fake sensor readings both to th
When `mongo_capture_config.uri` is configured, data capture will attempt to connect to the configured MongoDB server and write captured tabular data to the configured `mongo_capture_config.database` and `mongo_capture_config.collection` (or their defaults if unconfigured) after enqueuing that data to be written to disk.
635
688
636
689
If writes to MongoDB fail for any reason, data capture will log an error for each failed write and continue capturing.
Copy file name to clipboardExpand all lines: docs/data-ai/capture-data/advanced/how-sync-works.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -115,4 +115,4 @@ If your robot is offline and can't sync and your machine's disk fills up beyond
115
115
For more information, see [Automatic data deletion details](/data-ai/capture-data/advanced/how-sync-works/)
116
116
117
117
Data capture supports capturing tabular data directly to MongoDB in addition to capturing to disk.
118
-
For more information, see [Capture directly to MongoDB](/data-ai/capture-data/advanced/advanced-data-capture-sync/#capture-directly-to-local-mongodb).
118
+
For more information, see [Capture directly to MongoDB](/data-ai/capture-data/advanced/advanced-data-capture-sync/#capture-directly-to-your-own-mongodb-cluster).
0 commit comments