Skip to main content
Version: V3.2

Collector

The Collector page is where you configure connections that Capture uses to collect data from sources.

It provides:

  • A list of configured connections
  • Filtering and search to quickly find connections
  • A single entry point to create new connections (opens a separate page)

Connections tab​

The Connections tab shows all configured connections in a table.

The columns display:

  • Name: connection name
  • Type: connector type (for example, MQTT, ADS, ...)
  • Address: target host/address (when applicable)
  • Port: target port (when applicable)
  • Time Manager: whether this connection is marked as the time manager
  • Enabled/Disabled: whether the connection is enabled

Add a connection​

Use the Add action (+) to create a new connection.

Result: Capture opens the New connection page. This is a separate subpage documented here.

Use the Search field to filter the connection list by matching text (for example, name, type, or address depending on what is shown in the table).

Filters​

Use the filter panel to narrow down results. Common filters include:

  • Enabled: show enabled and/or disabled connections
  • Type: show only selected connection types
  • Time Manager: filter by time manager state

Filtering and search can be combined.

Settings tab​

These settings control how data collection buffers points in memory and when it flushes them to local storage.

tip

If you don't see this tab, you need to enable the Advanced options toggle in the top right.

Min storage available (MB)​

If available disk space on the disk where Capture is installed drops below this value (in MB), data collection is halted.

warning

When disk space is low, Capture will try to free space by removing oldest data from buckets without the Important flag. This cleanup can remove data even if it has not been synced yet.

Max buffer points​

Maximum number of datapoints kept in memory before being flushed to local storage (the configured local database).

When the in-memory buffer reaches this limit, Capture triggers an immediate flush.

Write timeout (ms)​

Flush interval in milliseconds for writing buffered points to local storage.

Flushing occurs:

  • every Write timeout interval, or
  • immediately when the number of buffered points reaches Max buffer points

Whichever happens first.

Copy Files To Local On Ingest (Edge Version 2.3+)​

This is the global setting for how the collector handles files it receives (see Files).

When enabled, every file received by the collector is copied to a local folder in the Capture data folder (default /etc/capture/data on Linux or C:\ProgramData\Capture\Data on Windows) and is synced to the cloud from there. After syncing, the local copy is removed if Delete local files after syncing is enabled in the Syncer.

When disabled, no copy is made and the original file path sent to the collector is used for syncing. The original file must still exist when the point is synced to the cloud. If Delete local files after syncing is enabled in the Syncer, the original file is removed after it is sent to the cloud.

info

This can also be overridden per file by adding createlocalcopy=false/true to your base64 string. See Files for details.

warning

When this option is disabled and Delete local files after syncing is enabled in the Syncer, the original file is deleted after syncing, not a copy.

Collect legacy System Monitoring data​

Enable this if you want the Monitoring measurement to be created and synced to the cloud. This measurement contains data about the system itself. On Edge versions 2.2.1 and newer, this is replaced by the more configurable and extensible System Metrics connection. The old Monitoring can still be enabled so existing dashboards using this data continue to work. It is recommended to disable this for new configurations, to avoid having the same data twice.