Skip to main content

3 posts tagged with "reduct-bridge"

View All Tags

Collect Host Metrics with the ReductBridge Metrics Input

· 9 min read
Alexey Timin
Co-founder & CTO - Database & Systems Engineering

Host CPU, memory, and disk metrics flow through the ReductBridge metrics input to ReductStore, alongside industrial and robotics data from MQTT on one shared time index

Every host already exposes how busy it is. For observability and deployment-health monitoring, CPU, memory, and disk usage show whether the system producing your data is healthy. The ReductBridge metrics input collects these host metrics automatically: no SDK in an application, no broker, and no robot. Give the bridge a config file on a host and it writes the metrics to ReductStore as time-indexed JSON records.

The same bridge instance can also collect industrial or robotics data through MQTT, such as camera frames or PLC telemetry. Host health and production data then share one time index, so "what was the CPU doing when this frame was captured?" is a direct correlation, not an exercise in reconciling two monitoring systems.

This post walks through collecting host metrics from an edge PC, storing them beside a camera stream, and querying both back over the same time window.

Record ROS 1 Topics in ReductStore with ReductBridge

· 8 min read
Anthony Cavin
Co-founder & CEO - Data, ML & Robotics Systems

A ROS 1 master publishes camera and IMU topics to the ReductBridge ros input, which writes them to two ReductStore entries on one shared time axis

ROS 1 Noetic reached end of life in May 2025, but a lot of robots still run on it. Recording data from them usually means rosbag files, or a custom recording node that you have to maintain yourself.

ReductBridge is another way to do it. It subscribes to topics on a ROS 1 master and stores each message it receives in ReductStore as a record, so you can query by time and by label later. It can also use the timestamp from the message header instead of the time the message arrived.

In this tutorial we'll record a camera topic and an IMU topic, set a retention limit, and read the data back with the ReductStore CLI and the Python SDK.

Capture Output from Legacy Equipment with the ReductBridge Shell Input

· 9 min read
Alexey Timin
Co-founder & CTO - Database & Systems Engineering

A legacy machine sends command output through the ReductBridge shell input to a time-indexed ReductStore entry

Plenty of equipment on the shop floor will never speak MQTT or OPC-UA. It predates both. What it has is a command line: a vendor tool that prints status, a diagnostic command on a serial console, or a script the previous engineer left behind. The data exists. There is just no protocol to integrate.

ReductBridge has a shell input for exactly this case. You point it at a command, set an interval, and the bridge runs it on schedule. Each line the command prints becomes a time-indexed record in ReductStore. Labels come from regex capture groups in the output or from static key-value pairs in the config. Wrap whatever the vendor tool prints, put it on an interval, label it, and it lands time-indexed beside everything else.

This post walks through capturing telemetry from a legacy test chamber that only exposes a chamber-status command.