Reduct Bridge

ReductBridge bridges live robotics and IIoT data with long-term storage in ReductStore. You can configure the bridge using a simple TOML file to define inputs, pipelines, and remotes. Inputs produce data, pipelines route and modify it, and remotes store it.

Inputs

An input is a data source. It reads data from a system and produces records for the bridge.

Supported input types include:

• HTTP - poll HTTP/HTTPS endpoints on a fixed interval and store response payloads with optional JSON/header label mapping.
• Metrics - collect host CPU, memory, and disk metrics as JSON records.
• MQTT - subscribe to MQTT v3/v5 topics over mqtt:// or mqtts:// and store raw payloads with optional payload/property label mapping.
• Shell - run shell commands on a fixed interval and store output lines as records.
• ROS1 - subscribe to ROS1 topics, store ROS messages, and extract labels from message fields.
• ROS2 - subscribe to ROS2 topics, store serialized CDR payloads, and extract labels from decoded message fields.

Remotes

A remote is a data destination. It receives records from pipelines and writes them to external storage.

Supported remote types include:

• ReductStore - write pipeline records and attachments to ReductStore with configurable batching.

Pipelines

Pipelines connect one or more inputs to one remote.

# Pipeline definition path:
# [pipelines.<pipeline_name>]
[pipelines.telemetry]

# Required: remote name from [[remotes.*]].
remote = "local"

# Required: one or more input names from [inputs.*.*].
inputs = ["ros_local"]

# Optional label rules (default = []):
# 1) Static labels:
#    { static = { source = "robot" }, to = "*" }
#    - adds labels to matching target entries
# 2) Copy labels from one entry to another:
#    { from = "time", labels = ["timestamp"], to = "echo" }
#    - remembers labels seen on matching source entries
#    - applies them to matching target entries
labels = [
  { static = { source = "ros1" }, to = "*" }
]

Supported Formats

ReductBridge supports different payload formats. Support means ReductBridge can parse payloads, extract labels, and, when schema information is available, store that schema in ReductStore.

• JSON: find values by field path (example: examples/mqtt_config.toml).
• HTTP input: poll HTTP/HTTPS endpoints and extract optional header/JSON labels (example: examples/http_config.toml).
• Protobuf: find values by field path (with schema) or by field ID/type (example: examples/mqtt_protobuf_config.toml).
• ROS formats: decode ROS message payloads for labels and store the payloads as records (example: examples/ros_config.toml).

Installation

ReductBridge is published in build types named after Cargo feature bundles: ros1, ros2, and iot. Choose the build type for the input family you need.

Build Types

Published packages and Docker images are split into these build types so each artifact only includes the dependencies needed for its input family.

Note: ROS2 binary and Docker artifacts are published per ROS distribution: ros2-jazzy and ros2-humble. The ROS2 snap is published as reduct-bridge-ros2 and currently uses the Jazzy build.

Input names in configuration use their input table names, for example [inputs.ros.*], [inputs.ros2.*], [inputs.mqtt.*], [inputs.shell.*], and [inputs.metrics.*].

Docker

Docker images are published as reduct/bridge:<tag>, where <tag> combines a release channel or version with the build type. For ROS2 Docker images, use the ROS distribution-specific build type: ros2-jazzy or ros2-humble.

```bash docker pull reduct/bridge:main- # development builds from main docker pull reduct/bridge:latest- # stable builds docker pull reduct/bridge:v- # release builds

File truncated at 100 lines see the full file

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[Unreleased]

0.5.1 - 2026-10-10

Fixed

• ROS package builds now use the pinned Rust toolchain instead of the distribution’s outdated system Cargo, PR-66.

0.5.0 - 2026-10-07

Added

• Optional per-topic qos = { reliability, durability, depth } for the ROS2 input, so latched (transient_local) and best_effort publishers can be recorded, PR-63.
• ROS 2 package metadata and CI coverage for building ReductBridge as a ROS package, PR-62.
• Snap packages now expose an optional reduct-bridge-configuration content plug for provider snaps that supply read-only TOML configuration files, PR-60.

Fixed

• The ROS2 input no longer fails when a configured topic is not advertised within 10 seconds. Advertised topics are subscribed immediately, the rest are retried once a second and subscribed as they appear, and a topic that fails to subscribe is skipped instead of stopping the others, PR-63.

0.4.1 - 2026-07-14

Fixed

• Relax nounset while sourcing ROS setup in the entrypoint, PR-54.

0.4.0 - 2026-06-25

Changed

• Hardened the build supply chain by pinning Rust 1.96.0 in-repo, enforcing locked Cargo installs in CI/coverage, digest-pinning CI Docker base images, and verifying the ROS apt key fingerprint during image builds.
• ROS1/ROS2 schema metadata is now stored under the $schema attachment key by default, falling back to the legacy $ros key for entries that already carry one, PR-51.

0.3.1 - 2026-06-04

Fixed

• Fixed periodic attachment resend skipping cached attachments when the entry is missing, PR-49.
• ROS2 topic timestamp mapping from decoded message fields, including config validation, PR-47.

0.3.0 - 2026-06-02

Added

• HTTP input for polling HTTP/HTTPS endpoints on a fixed interval with GET requests, optional bearer/basic auth, header/static/JSON field label mapping, and HTTP-specific tests and documentation, PR-33.
• Optional ReductStore bucket creation via [remotes.reduct.create_bucket], with configurable quota_type, numeric or human-readable quota_size values such as "1GB" and "4GiB", updated examples/docs, and parsing coverage for valid and invalid unit strings, PR-34.
• Reduct remote attachment reconciliation with attachments_resend_interval_ms (default 300000, 0 disables) to periodically restore missing attachments, including config/docs coverage and CI tests for enabled/disabled behavior, PR-45.
• Timestamp mapping from source data fields, headers, and MQTT v5 user properties for HTTP, MQTT, and ROS1 inputs, with shared parsing for Unix, ISO8601, and ROS stamp formats, PR-46.
• Protobuf support for MQTT input with schema-based decoding, wire-format field extraction, dynamic labeling, and descriptor attachments, PR-31

Changed

• Bundle-style ros1, ros2, and iot build features with CI and installation documentation updates, PR-37.
• Improved Reduct create_bucket quota UX by defaulting quota_type to NONE, requiring quota_size only for FIFO/HARD, and aligning launch/config validation and docs with this behavior, PR-43.
• Preferred keyed TOML syntax for Reduct remotes ([remotes.reduct.<name>]) while keeping [[remotes.reduct]] backward compatible, now with deprecation warnings when the legacy array syntax is used, including updated docs/examples and parser coverage, PR-42.

0.2.1 - 2026-05-19

Fixed

• Docker image pipeline now builds per variant with Ubuntu base selection, non-root runtime, ROS2 runtime provisioning for ROS variants, corrected DockerHub tagging, and SBOM/provenance attestations, PR-36

0.2.0 - 2026-05-11

Added

• Metrics input for CPU, memory, and disk with JSON output and label mapping, PR-19
• MQTT input for MQTT v3/v5 with payload/topic labels and optional JSON-schema attachments, PR-24

Fixed

• Deterministic bridge shutdown by tracking component tasks, PR-22
• Pinned third-party GitHub Actions to immutable commit SHAs in CI workflow hardening, PR-32

0.1.2 - 2026-03-30

Added

• Official Snap packaging, ROS1/ROS2 variant build matrix, CI publish workflow, and README installation docs, PR-12

Fixed

• Patched ROS1 rosrust/xml-rpc dependencies to address security issues, PR-17

0.1.1 - 2026-03-19

Fixed

• ROS2 wildcard discovery, exact-topic label extraction, recursive schema attachments, and ReductStore timestamp/path handling, PR-6

0.1.0 - 2026-03-18

Added

File truncated at 100 lines see the full file