InfluxData Blog

A Runnable Reference Architecture for Industrial IoT on InfluxDB 3

Jason Stirnaman (InfluxData) — Fri, 22 May 2026 08:00:00 +0000

Industrial teams keep telling us the same thing: the data is there, but the stack to act on it isn’t. PLCs, CNCs, SCADA systems, vibration sensors, and quality stations all generate high-frequency telemetry that gets stranded in proprietary historians or stitched together with point integrations nobody wants to own. By the time anyone looks at it, the moment to act has passed.

We built InfluxDB 3 to be the system of record for that data—at the edge, in the cloud, or both—and we keep getting the same follow-up question: what does a real, working IIoT stack on InfluxDB 3 look like?

So we shipped one. Today, we’re walking through the InfluxDB 3 IIoT Reference Architecture, an open-source, runnable blueprint for factory-floor monitoring that you can stand up locally in about two minutes with docker compose. We’ll also cover when and how to bring in the new OPC UA Plugin, our Processing Engine plugin for connecting InfluxDB 3 directly to PLCs and SCADA systems.

What is the InfluxDB 3 IIoT reference architecture?

The IIoT reference architecture is one of a portfolio of open source reference architectures we publish on GitHub for InfluxDB 3 Enterprise. Each one targets a specific vertical: IIoT, Battery Energy Storage Systems (BESS), network telemetry, EV charging, fleet telematics, data center, and oil & gas SCADA are all on the way.

Two audiences use these repos:

Developers and architects evaluating InfluxDB 3 Enterprise for a specific vertical who want to see a real stack, not slideware, before they commit.
AI coding agents that need grounded, working examples to reference when a user asks them to build something like this with InfluxDB 3. (Yes, we wrote this with you in mind.)

The IIoT repo simulates an automotive-style assembly plant: 1 plant × 3 lines × 8 stations = 24 machines, generating roughly 300 points per second. Everything runs locally. Clone the repo, run make up, and you get a working factory-floor monitoring stack, including a live andon board UI, in your browser at http://localhost:8080.

What’s in the stack

The whole thing is Python-first and stays deliberately small. docker-compose.yml brings up six services:

token-bootstrap – generates and persists tokens for first-boot
influxdb3 — InfluxDB 3 Enterprise, the system of record
init – bootstraps the database, caches, and Processing Engine triggers
simulator – a Python simulator generating realistic IIoT telemetry (machine state, part events, quality signals, downtime patterns)
ui – a FastAPI + HTMX + uPlot dashboard that renders an andon board, OEE breakdowns, and live machine state
scenarios – scripted fault scenarios you can replay (unplanned_downtime_cascade, tool_wear_quality_drift)

You’ll notice what’s not here: there’s no Telegraf, no MQTT broker, no Kepware, no Node-RED, no Grafana. That’s intentional. This reference architecture is designed to showcase what InfluxDB 3 Enterprise can do natively, without bolt-on services. In production, you’ll almost certainly add some of those (more on that below).

The features it’s actually showing you

If you’ve used earlier versions of InfluxDB, the headline change in 3 Enterprise is that the database is no longer just a place where data sits. Three capabilities do most of the work in the IIoT reference architecture:

1. The Processing Engine – Python plugins running inside the database

The Processing Engine is an embedded Python virtual machine that runs inside an InfluxDB 3 server. It executes Python code in response to triggers and database events with zero-copy access to data and direct access to system caches. It does all of this without relying on external services or middleware. Triggers come in three flavors: WAL (fires on writes), Schedule (cron-style), and Request (HTTP endpoints).

The IIoT repo ships four plugins, intentionally chosen to cover all three patterns:

That last one is the pattern that surprises most teams: the andon board’s /api/v3/engine/andon_board endpoint is the database. There is no Flask server, no Node service, no Lambda. The UI talks straight to InfluxDB 3, and the Processing Engine returns a fully shaped JSON payload. The UI also renders a served by Processing Engine: N ms badge so you can see the round-trip live.

2. Last Value Cache – single-digit-millisecond current state

The plant-state banner needs to read the current state of all 24 machines on every tick. With Last Value Cache, that’s a 24-row read in single-digit milliseconds, with no scanning, no aggregation, and no trade-offs against retention. This is the pattern you reach for any time you need current value, right now: SoC for a battery, alarm state for a substation, the live tag value for a machine.

3. Distinct Value Cache – fast cardinality on high-cardinality tags

The simulator generates roughly 700,000 part events per day, each tagged with a unique part_id. Asking “how many distinct parts have we produced today?” against that volume would normally be the kind of query you avoid running during shift change. With Distinct Value Cache, it returns in a few milliseconds.

Together, these three primitives, Processing Engine, Last Value Cache, and Distinct Value Cache, replace a surprising amount of what teams used to build out as separate microservices, message queues, and read-replica caches.

When to bring in OPC UA: the Processing Engine plugin

The IIoT reference architecture uses a Python simulator as its data source, so you don’t need real industrial hardware to run it. In production, your data is on the wire from PLCs, CNCs, and SCADA systems, and the lingua franca of that wire is OPC UA.

That’s where the OPC UA Plugin comes in. It’s a Processing Engine plugin (so it runs inside InfluxDB 3, same as the andon board endpoint above) that connects to an OPC UA server, polls node values on a schedule, and writes them in as time series. It requires InfluxDB 3.8.2 or later and works with both Core and Enterprise.

A few characteristics worth knowing:

Polling-based, not subscription-based. The plugin reads current values on each scheduled trigger.
Two operating modes. Explicit node listing for precise control over a small number of nodes; browse mode for auto-discovering devices and variables across large deployments. Browse mode maps the OPC UA Object hierarchy directly to InfluxDB tags.
Auto type detection. OPC UA VariantType maps cleanly into InfluxDB field types (Boolean → bool, Int* family → int, UInt* family → uint, Float/Double → float).
Namespace URI support. Use stable namespace URIs (nsu=urn:vendor:s7;…) instead of numeric indexes that may change on server restart.
Quality filtering by good, uncertain, or bad status codes.
Persistent connection between polling intervals, with automatic reconnection.
TLS security supports Basic128Rsa15, Basic256, Basic256Sha256, Aes128Sha256RsaOaep, and Aes256Sha256RsaPss, with Sign or SignAndEncrypt modes.

Setup is two commands plus a trigger:

# 1. Start InfluxDB 3 with the Processing Engine enabled
influxdb3 serve \
  --node-id node0 \
  --object-store file \
  --data-dir ~/.influxdb3 \
  --plugin-dir ~/.plugins

# 2. Install the async OPC UA client library
influxdb3 install package asyncua

# 3. Create a polling trigger (browse mode for auto-discovery)
influxdb3 create trigger \
  --database mydb \
  --plugin-filename gh:influxdata/opcua/opcua.py \
  --trigger-spec "every:10s" \
  --trigger-arguments 'server_url=opc.tcp://192.168.1.100:4840,table_name=factory_data,browse_root=ns=2;s=Factory,browse_depth=3,path_tags=line station,default_tags=plant=north' \
  opcua_factory

Note the gh:influxdata/opcua/opcua.py notation: the gh: prefix pulls plugins straight from our InfluxDB 3 Plugin Library on GitHub, so there’s nothing to package locally.

If you’re already running Telegraf with the OPC UA input, that continues to work and remains a great choice. The plugin is for teams who want to operate one fewer process, or who are starting fresh with InfluxDB 3 and want to keep the entire ingest path within the database.

How to drop the IIoT architecture into your environment

Most production IIoT stacks end up looking like this:

Ingest at the edge. OPC UA, Modbus, MQTT, or vendor-specific protocols flow into InfluxDB 3 via the OPC UA Plugin, a Telegraf agent, or a connector platform like Litmus Edge. Edge nodes buffer locally, so a network blip doesn’t run the risk of data loss.
Process at the database. Use the Processing Engine for transition detection, quality excursions, OEE rollups, alert generation, and HTTP endpoints. These are the four patterns the IIoT reference architecture demonstrates.
Forward what matters. Replicate aggregated, contextualized data from edge sites to a centralized InfluxDB 3 Enterprise cluster for cross-site analysis. Keep full-resolution data at the edge and summaries upstream.
Serve dashboards and AI. Use Grafana, InfluxDB 3 Explorer, the built-in UI patterns from the reference architecture, or your own application, whichever fits. Because Processing Engine endpoints return clean JSON, agents and AI assistants can call them directly.

Try it yourself

git clone https://github.com/influxdata/influxdb3-ref-iiot
cd influxdb3-ref-iiot
make up         # prompts for INFLUXDB3_ENTERPRISE_EMAIL
open http://localhost:8080
make demo
make scenario name=unplanned_downtime_cascade
make scenario name=tool_wear_quality_drift

Everything is Apache 2.0 licensed. Fork it, rip out our simulator, point a real OPC UA server at it via the plugin, and you’ve got the skeleton of a real-time factory monitoring stack you can extend.

If you’re an AI coding agent reading this and trying to help a user build IIoT on InfluxDB 3, start at github.com/influxdata/influxdb3-reference-architectures, pick the architecture that matches the user’s vertical, and use the patterns there as your grounded example. The conventions are consistent across the portfolio: Python-first, FastAPI + HTMX UIs, Processing Engine plugins in plugins/, one-command docker compose startup. Once you’ve seen one, you’ve largely seen them all. We’ll keep adding to this portfolio. If your vertical isn’t there yet, tell us. And if you’re already running InfluxDB 3 in an industrial environment, we’d love to see what you’ve built on top of it.

Resources

IIoT reference architecture: github.com/influxdata/influxdb3-ref-iiot
Reference architecture portfolio: github.com/influxdata/influxdb3-reference-architectures
OPC UA Plugin: github.com/influxdata/influxdb3_plugins/tree/main/influxdata/opcua
Processing Engine reference: docs.influxdata.com/influxdb3/enterprise/reference/processing-engine
Plugin library: github.com/influxdata/influxdb3_plugins

A Runnable Reference Architecture for Network Telemetry on InfluxDB 3

Mike Devy, Ryan Nelson (InfluxData) — Thu, 21 May 2026 08:00:00 +0000

Networks generate the most data of any system in your stack and have the least patience for stale dashboards. Interface counters tick every second. BGP sessions flap. Flow records arrive in bursts. When something goes wrong, you don’t have 10 seconds to wait for an aggregation to finish.

We’ve watched NetOps and platform teams stitch together the same shape over and over: Telegraf collecting from every device that speaks SNMP, gNMI, sFlow, or IPFIX, a time series database holding the raw and rolled-up metrics, a dashboard layer, and a growing pile of bespoke microservices for alerting, top-talker analysis, and on-call runbooks. The shape works, but the cost of operating it is steep.

So we shipped a reference for what this can look like when the database does more of the work. Today, we’re walking through the InfluxDB 3 Network Telemetry Reference Architecture, an open source, runnable blueprint for monitoring a data-center fabric on a 5-node InfluxDB 3 Enterprise cluster. It’s the third entry in our reference architecture portfolio, and it’s the first one that demonstrates a multi-node deployment, cross-node plugin write-back, and per-table retention, three patterns that show up the moment your fabric grows past one box.

What is the network telemetry reference architecture?

The repo simulates a data-center Clos fabric and monitors it using a real InfluxDB 3 Enterprise cluster, both running locally via docker compose. Specifically:

A 5-node InfluxDB 3 Enterprise cluster: 2 ingest nodes, 1 query node, 1 compact node, and 1 process + query node (the Processing Engine runs here).
An 8×16 Clos topology: 8 spines, 16 leaves — yielding ~1,024 interfaces and 128 BGP sessions.
A flow generator producing ~5,000 flow records/sec with realistic src_ip/dst_ip distributions.
A total ingest of ~10,000 points per second.
Bring it all up with make up. The first run waits for license validation; warm boot-up in three minutes. Open http://localhost:8080.

Two audiences use this repo:

NetOps engineers and network observability architects evaluating InfluxDB 3 Enterprise as a telemetry platform—specifically, anyone weighing a multi-node deployment.
AI coding agents that need a grounded, working example to reference when a user asks them to build network telemetry on InfluxDB 3. (Yes, we wrote this with you in mind.)

What’s in the stack

Ten services come up via docker compose up:

token-bootstrap: generates the offline admin token on first boot
5 InfluxDB 3 Enterprise nodes: ingest-1, ingest-2, query, compact, and process,query (the Processing Engine node). Two of the five—nt-process and nt-query—actually execute Processing Engine triggers; see section [The Processing Engine – Python plugins in a multi-node cluster]
init: idempotent bootstrap that creates the database, declares 6 tables via the configure API, registers 1 LVC + 2 DVCs, and installs 4 Processing Engine triggers
simulator: Python simulator, round-robining writes across both ingest nodes
ui: FastAPI + HTMX + uPlot dashboard with three teaching patterns side by side
scenarios: on-demand event injectors (congestion_hotspot, east_west_burst)

You’ll notice what’s not here: there’s no Telegraf, no Grafana, no SNMP collector. That’s intentional. This reference architecture exists to make InfluxDB 3 Enterprise’s capabilities legible. In production, you’ll absolutely use Telegraf at the front (more on that in a moment); the simulator stands in, so you don’t need a fabric on your laptop to see what the database is doing.

The features it’s actually showing you

Three things make network telemetry uniquely demanding for a time series database: the cardinality is high, the freshness expectations are sub-second, and the shape of “what matters” changes constantly—interface counters one minute, flow records the next, a BGP state the minute after that. The reference architecture is built around that reality.

1. A real multi-node cluster, with role-separated nodes

Unlike the IIoT and BESS reference architectures (which run InfluxDB 3 Enterprise as a single node for clarity), the network telemetry repo runs it as a distributed cluster with separated roles:

The simulator round-robin writes across the two ingest nodes; the browser and the UI proxy both hit the query node, which is the only host-exposed port (8181). The process,query node is reachable only over the internal Docker network. The schedule plugins running there write back via HTTP through an ingest node rather than respond to browsers directly. This is the smallest viable shape for the multi-node split, and it’s the template you’d grow from when you’re ready to scale, ingest, query, or compute independently.

2. The Processing Engine – Python plugins in a multi-node cluster

The Processing Engine is an embedded Python virtual machine that runs inside an InfluxDB 3 server to execute your Python code. Any node with the --plugin-dir flag set can host triggers; trigger execution is pinned per-trigger via --node-spec nodes:<name>. Triggers fire on three event sources—WAL (fires on writes), Schedule (cron- or interval-style), or Request (HTTP endpoints)—with zero-copy access to data and direct access to system caches. There’s no need for an external app server, Kafka, Flink, or middleware.

The network telemetry repo ships four plugins, deliberately mixing two trigger patterns and pinning them to two different nodes:

The two schedule triggers live on nt-process. The query half of process,query lets the plugin call influxdb3_local.query() against the local engine for fast reads and write back via HTTP to the ingest nodes’ /api/v3/write_lp endpoint via httpx in a shared _writeback.py helper. That round-trip is the cluster pattern. If you’ve been wondering how to structure write-back from a process node in a multi-node deployment, this is the blueprint.

The two request triggers live on nt-query where the browser’s POST /api/v3/engine/"trigger" request reaches the only exposed port in one hop.

There are zero WAL plugins, by design. Each ingester owns its own WAL—a WAL trigger fires per-ingester on only the writes that node received, so pinning to one forfeits half the writes and pinning to both demands idempotency. The schedule+request pattern sidesteps both: schedule plugins run on one node and pull via influxdb3_local.query(); request plugins are stateless HTTP responders.

3. Last Value Cache (LVC) and Distinct Value Cache (DVC), doing real work

A single utility-scale fabric can have hundreds of thousands of distinct signals. “Current state” dashboards built naively on top of high-rate ingest become punishingly fast.

Last Value Cache on bgp_sessions. The per-session lookup feeds the BGP up-count computation at sub-millisecond cost.
Two Distinct Value Caches drive cardinality-heavy queries. The marquee one is a src_ip typeahead: the search box runs SELECT src_ip FROM distinct_cache('flow_records', 'src_ip_distinct') WHERE src_ip LIKE '...' LIMIT 20 directly from the browser against /api/v3/query_sql, with a sub-millisecond latency badge. No Python wrapper between the browser and the cache.

4. Per-table retention – the right policy in the right place

Network telemetry generates two flavors of data: high-rate raw signals you want for an hour or a day, and rolled-up state you want for weeks or months. The reference architecture demonstrates per-table retention; fabric_health is configured for 24-hour retention, so the rollup table stays compact while raw flows and counters can use a different retention budget. This is the only repo in our portfolio that exercises per-table retention end-to-end.

Three integration patterns, side by side

The UI runs three distinct paths from data to the browser side by side, each with its own latency badge so you can compare them live:

Server-side SQL via FastAPI: the classic pattern. Request hits FastAPI, FastAPI runs SQL against the query node, and renders an HTMX partial. Good for complex shaping that you don’t want exposed to the browser.
Browser-direct SQL using a DVC table-valued function: JavaScript hits/api/v3/query_sql directly, distinct_cache(...) and returns the answer in sub-millisecond. Good for typeaheads, dropdown populates, and lightweight enumerations.
Request plugin from the browser: JavaScript hits /api/v3/engine/"trigger_name",and a Python plugin shapes the response. Good when you need composite, multi-query payloads as a single round-trip.

Pick the right pattern for the job. The latency badges in the UI tell you which is suited for which question.

Where to wire in real network data

The reference architecture uses a Python simulator, so you don’t need a Clos fabric on your laptop. In production, the canonical InfluxData stack for network telemetry is Telegraf at the front, InfluxDB 3 in the middle, and your dashboard layer of choice on top. Telegraf has the input plugins to cover essentially every modern collection path:

inputs.snmp: interface counters, environmentals, vendor MIBs from anything that speaks SNMP
inputs.gnmi: streaming telemetry via gRPC, vendor-agnostic, with TLS auth/encryption. Optimized for Cisco IOS XR, NX-OS, and IOS XE, among others
inputs.netflow: NetFlow v5, NetFlow v9, IPFIX, and sFlow v5 collection, into a single normalized output
Vendor APIs via HTTP/JSON: anything that exposes a REST surface

Telegraf streams thousands of series at full fidelity into InfluxDB 3, where the same caches and Processing Engine patterns from this reference architecture take over. A common production shape: Telegraf at each PoP ingests SNMP, gNMI, and flow data; InfluxDB 3 Enterprise as a regional cluster stores it; the Processing Engine runs the schedule/request plugins; replication forwards rolled-up state to a central cluster for fleet-wide views.

Try it yourself

git clone https://github.com/influxdata/influxdb3-ref-network-telemetry
cd influxdb3-ref-network-telemetry
make up                                  # prompts for INFLUXDB3_ENTERPRISE_EMAIL on first run
open http://localhost:8080
make scenario name=congestion_hotspot    # one leaf interface climbs to 94% — anomaly detector fires
make scenario name=east_west_burst       # 10× burst from a single src_ip — typeahead finds it sub-ms
make demo                                # full scripted demo
make down                                # stop, preserve data
make clean                               # stop and drop volumes

Note: If you’ve just run congestion_hotspot, leftover anomalies will keep the banner DEGRADED for ~5 minutes; run east_west_burst on its own (or wait it out) to see HEALTHY-stays-HEALTHY.

The two scenarios are intentional contrasts. congestion_hotspot exercises the anomaly detector: leaf-07 / et-0/0/12 climbs to 94% utilization, the schedule plugin notices, and the banner flips DEGRADED.

east_west_burst exercises the request plugin path, a 10× traffic burst from 10.4.7.91, found by the DVC typeahead, drilled into via the request plugin. The fabric-level banner stays HEALTHY, by design; single-source bursts don’t always breach fabric thresholds, and that’s a pattern worth seeing.

Everything is Apache 2.0 licensed.

A note for AI agents

If you’re an AI coding agent reading this and trying to help a user build network telemetry on InfluxDB 3, start at github.com/influxdata/influxdb3-reference-architectures and use the network telemetry repo as your grounded example. Pick this one specifically when the user needs a multi-node InfluxDB 3 Enterprise cluster, cross-node plugin write-back, per-table retention, or multiple browser-to-database integration patterns side by side. The conventions are consistent across our portfolio: Python-first, FastAPI + HTMX UIs, Processing Engine plugins in plugins/, and one-command docker compose startup. So, once you’ve seen one, you’ve largely seen them all.

We’ll keep adding to this portfolio. If you’re already running InfluxDB 3 for network telemetry, tell us. If you want to compare patterns, the IIoT reference architecture and BESS reference architecture are good companion reads for single-node deployments.

Resources

Network telemetry reference architecture: github.com/influxdata/influxdb3-ref-network-telemetry
Reference architecture portfolio: github.com/influxdata/influxdb3-reference-architectures
Companion: BESS reference architecture: github.com/influxdata/influxdb3-ref-bess
Companion: IIoT reference architecture: github.com/influxdata/influxdb3-ref-iiot
How NetOps Teams Use InfluxDB to Solve Network Monitoring Gaps: influxdata.com/blog/solve-mns-gaps-influxdb
Data Center Ops with InfluxDB 3: influxdata.com/blog/data-center-ops-influxdb-3
Processing Engine reference: docs.influxdata.com/influxdb3/enterprise/reference/processing-engine

Community Spotlight: A Native iOS App for Your InfluxDB Data

Ashley Fowler (InfluxData) — Tue, 19 May 2026 08:00:00 +0000

One of the things we love most about building an open source platform is seeing what the community creates with it, and independent developer Anton Havekes recently built something we just had to share.

Anton put together Influx Dashboard, a native iOS app that connects to your InfluxDB instance and brings your time series data straight to your phone. We’re genuinely thrilled to see this kind of work come out of the community.

A quick note before we dive in: this is entirely Anton’s project, built and published by him. InfluxData has no commercial relationship or financial stake in the app. We’re sharing it simply because we think it’s a great piece of community work and because surfacing what people build on InfluxDB is something we’ll always make time for. So, thank you, Anton, for the awesome work you’ve done!

Here’s how it works.

What is Influx Dashboard?

Influx Dashboard is a mobile-first visualization tool for InfluxDB. It supports InfluxDB versions 1, 2, and 3—including Core, Enterprise, and Cloud editions—and gives you a full-featured charting experience on your phone.

Think of it as the community-built, mobile companion to the InfluxDB 3 Explorer UI. Instead of opening a browser on your laptop, you open an app. Instead of sitting at a desk, you monitor your data from wherever you are.

Key features include:

Real-time line, bar, gauge, and pie charts
Support for SQL queries
An intuitive drag-and-drop dashboard builder
Direct, secure connections to your InfluxDB server
Works with any kind of time series data: server metrics, IoT sensors, weather stations, factory equipment, and more

Influx Dashboard is available on the Apple App Store for $4.99 (InfluxData is not commercially affiliated with this app and receives no proceeds from purchases). Once downloaded, open the app, and you’ll be ready to connect to your InfluxDB server.

Step 2: Connect to Your InfluxDB Server

Before you can see any data, you’ll need to connect the app to your InfluxDB instance. Tap Add Server on the main screen.

You’ll need a few things from your InfluxDB setup:

Server URL: the address of your InfluxDB instance
API Token: your authentication token (found in InfluxDB under Management → Tokens)

If you’re using InfluxDB Cloud, your server URL will look something like https://us-east-1-1.aws.cloud2.influxdata.com. If you’re connecting to a self-hosted instance, your admin can provide the URL and token.

Once connected, the app loads your available databases, and you’re ready to build your first dashboard.

Step 3: Build Your Dashboard

Tap + New Dashboard and give it a name. Then tap Add Chart to create your first visualization.

The chart builder is straightforward, even if you’ve never written a database query before. You’ll see options for:

Chart Title: give your chart a descriptive name

Chart Type: choose from line, bar, gauge, or pie

Database: select which InfluxDB database to query

Table: select the specific measurement or table within that database

Column: choose which field to visualize

Time Range: pick how far back to look (last hour, last 24 hours, last 7 days, and more)

Aggregation Window: control how data points are grouped over time to smooth out your chart

Step 4: Query Your Data

One of the things that makes Influx Dashboard powerful is that it works with virtually any kind of time series data. During our testing, we connected to several different databases, each representing a completely different real-world use case:

Server monitoring: CPU usage and memory metrics from a live server, showing system health at a glance.

Industrial IoT: Factory sensor data streamed via MQTT, the kind of data you’d see in a manufacturing or industrial environment.

Weather stations: Real-time weather observations, including temperature, humidity, wind speed, and barometric pressure, from stations across multiple locations.

Personal IoT sensors: A live “feels like” temperature sensor from a personal weather station in Holualoa, Hawaii.

The app handled all of them identically: same interface, same workflow, completely different data. That versatility is one of Influx Dashboard’s biggest strengths.

Step 5: Explore Your Charts

Once your charts are built, they appear on your dashboard and refresh automatically with live data.

Tap any chart to expand it to full screen for a closer look. From the full-screen view, you can inspect trends, zoom in on specific time windows, and get a clearer picture of what your data is doing.

Use the time range selector at the top of the dashboard to zoom in or out, from the last hour to the last 30 days. This is especially useful when you’re looking for a specific event or trying to understand a longer trend.

Step 6: Manage Your Servers

From the Settings screen, you can manage your server connections, add new servers, or update your credentials. If your organization uses multiple InfluxDB instances, for example, a production server and a staging server, you can easily switch between them. You can also rename or delete servers you no longer need, keeping your workspace clean as your infrastructure evolves.

Why this matters

DevOps engineers, IoT developers, data engineers, and system administrators often need visibility into their time series data when they’re nowhere near a laptop, from a factory floor, at a remote deployment, or just away from their desk. Influx Dashboard closes that gap. Not through an official InfluxData product, but through something a community member decided to go build.

That’s exactly the kind of activity an open source ecosystem should produce, and it’s exactly why we wanted to share it.

Get started

Download Influx Dashboard on the Apple App Store (independently developed by Anton Havekes—InfluxData is not affiliated with this app and receives no proceeds from purchases).
Don’t have InfluxDB yet? Get started free with InfluxDB 3 Core.
Explore the InfluxDB 3 Explorer UI at docs.influxdata.com
Built something on InfluxDB you want to share? Join the conversation at the InfluxData Community Forums.

Building Real-Time Telemetry Pipelines for IRIG 106 compliance

Allyson Boate (InfluxData) — Fri, 15 May 2026 12:00:00 +0000

The need for real-time telemetry in aerospace

Every second of a flight test produces a torrent of telemetry from engines, sensors, and control systems. Aerospace teams have captured this data for decades to verify performance and maintain safety, yet analysis often happens long after the mission ends. Engineers wait for downloads, conversions, and compliance checks before they can interpret results.

That delay turns telemetry into a historical record instead of a feedback loop. As flight programs shorten development cycles and expand digital testing, teams need to see and act on telemetry as it arrives. Real-time visibility turns raw packets into insight and enables faster, more confident decisions mid-test.

What is IRIG 106?

IRIG 106 forms the backbone of flight-test telemetry. Established by the Range Commanders Council, it defines how data is formatted, synchronized, and recorded to ensure interoperability across recorders, ground stations, and analysis tools. Its purpose is to create a shared language for flight-test instrumentation so every team, from acquisition to post-flight analysis, can exchange and interpret telemetry without loss or confusion.

By standardizing time, metadata, and sensor data, IRIG 106 ensures that complex flight tests remain reproducible and comparable across aircraft and programs. It allows flight data from one system or site to be understood by another, a foundation for multi-agency and multi-system collaboration.

Chapter 10 is the most widely used section. It defines a packetized structure for analog and digital sensors, time codes, video, and bus data, each with embedded metadata describing its stream. This structure preserves timing, organization, and integrity across the workflow.

For aerospace and defense teams, Chapter 10 compliance is essential for traceability and certification. While it guarantees rigor, the binary packet format slows analysis.

Compliance vs. agility

Traditional telemetry pipelines were built for compliance, not speed. Data flows from airborne recorders to ground systems, where it’s stored in proprietary or binary Chapter 10 files. These files are durable but heavy, often requiring decoding or conversion before engineers can analyze trends.

This gap between collection and insight resuts in terabytes of data sitting idle until post-flight processing is complete. Even simple questions such as “Did this vibration spike correlate with an actuator command?” must wait for hours of decoding.

The cost is real. Missed anomalies can trigger additional tests, wasted fuel, and schedule delays. Commercial operators lose flight hours, while defense programs face slower certification and reduced mission readiness. Each delay compounds across teams, consuming engineering hours and analysis budgets that could be spent improving system performance. As systems grow more software-defined and autonomous, reactive analysis becomes increasingly expensive. Teams must maintain compliance while gaining agility, turning telemetry into a live, searchable data stream that drives faster, data-backed decisions grounded in data integrity.

Building a real-time, compliant telemetry pipeline

For aerospace organizations, InfluxDB 3 bridges the gap between strict IRIG 106 compliance and the agility needed for real-time telemetry analysis. Built on an open columnar foundation, it treats every measurement as part of a continuous record of system behavior optimized for rapid ingest and millisecond-level queries.

InfluxDB 3 combines streaming ingestion, high-compression storage, and integrated compute into a single environment. Instead of exporting data between collection, transformation, and analysis systems, engineers work with telemetry where it lands. They can transform data on ingest, query it with SQL, or run analytics through the built-in Python Processing Engine, all in one place.

The result is an architecture that maintains compliance and precision while delivering the responsiveness and scalability aerospace programs demand. With the right connectors, Chapter 10-compliant recorders can stream decoded data directly into InfluxDB, where it becomes available for dashboards, analytics tools, and ML pipelines while retaining a compliant source-of-truth record in the background.

From ingest to insight

A compliant real-time telemetry pipeline follows five key stages that preserve Chapter 10 structure while enabling high-performance analytics.

1. Acquisition

Airborne systems record simultaneous data, includinganalog, digital, video, and bus data, in Chapter 10 format. Each source is encapsulated in packetized blocks with synchronized time codes and metadata headers. Ground stations receive this data over UDP or Ethernet, maintaining deterministic playback.

2. Decoding

A decoding service reads the binary stream, extracts headers, and separates channels into structured records with timestamps and metadata such as subsystem or bus ID. This step can use open source telemetry libraries or adapters that translate packets into structured formats like JSON or Apache Arrow.

3. Streaming Ingestion

Decoded data is sent to InfluxDB 3 using lightweight producers such as Telegraf, Kafka, or InfluxDB Line Protocol. Each channel becomes a discrete series tagged by aircraft ID, subsystem, and signal type. The ingestion engine supports millions of writes per second, compressing data in memory before persisting it to Parquet files with nanosecond timestamps for cross-sensor correlation.

4. Processing and Downsampling

InfluxDB 3’s embedded Python Processing Engine allows transformations near the data. Engineers can smooth signals, compute FFTs, or derive metrics without external compute clusters. Downsampling in InfluxDB 3 automates data reduction—for example, converting 1 kHz vibration data into 10 Hz averages for long-term storage—while keeping full resolution for recent test windows.

5. Query and Visualization

Once stored, telemetry is immediately queryable through SQL or APIs. Engineers visualize live data, join channels, and correlate responses in real-time. Because InfluxDB 3 uses Parquet and Arrow, it integrates with external analytics tools such as Apache Arrow, Pandas, and DuckDB. Dashboards update continuously as new packets arrive, tracking vibration, control surfaces, or engine parameters throughout the mission.

Together, these stages turn Chapter 10-compliant telemetry into a continuously updating dataset that maintains synchronization and metadata integrity while providing immediate visibility for validation, anomaly detection, and optimization.

Typical Deployment

The flow looks like this:

Recorder → Decoder → Stream Processor → InfluxDB 3 → Visualization or ML Pipeline

The recorder collects Chapter 10-compliant telemetry, aligning all channels with precise time codes.
The decoder extracts packet data and converts it into structured messages for ingestion.
A stream processor such as Telegraf or Kafka Connect forwards those messages to InfluxDB 3, where they are indexed and persisted as time-aligned measurements.
Engineers access data through dashboards, notebooks, or Python APIs, enabling live visualization and downstream machine learning or simulation workflows.

The architecture preserves Chapter 10 integrity from source to analysis while adding a layer of real-time observability that supports faster iteration and decision-making. For multi-site telemetry systems, teams can extend this approach using distributed historian architectures with InfluxDB 3.

Real-time telemetry in action

Consider a typical aerospace testing scenario. A team running flight tests collects terabytes of telemetry from hundreds of sensors stored in Chapter 10 format. Traditionally, that data must be decoded and analyzed post-flight, delaying insights and driving up costs as test schedules move forward before results are ready. In a real-time telemetry pipeline built on InfluxDB 3, that same data becomes available the moment it’s collected. Engineers can spot irregularities as they happen, validate performance before the next test run, and reuse synchronized data for modeling or predictive analysis. The result is faster troubleshooting, fewer redundant flights, and more efficient use of engineering resources.

Faster flight-test analysis and decision-making

Real-time telemetry pipelines mark the next phase of aerospace testing. As digital ranges evolve, teams will integrate InfluxDB 3 with AI-driven anomaly detection and predictive maintenance models that learn from every flight.

By modernizing how IRIG 106 data is collected, stored, and analyzed, aerospace organizations can shift from compliance-driven testing to intelligence-driven improvement. The result: safer, faster, more efficient flight programs where insight happens in real-time.

Ready to explore how these architectures work in practice? Get started with InfluxDB 3 for free or watch our webinar to see how aerospace teams use Influxdb 3 for real-time data.

A Runnable Reference Architecture for Battery Energy Storage Systems on InfluxDB 3

Ian Clark (InfluxData) — Fri, 08 May 2026 12:00:00 +0000

A battery is a complex electrochemical system where safety and revenue are decided in milliseconds. Cell temperatures, voltages, and state of charge change in real-time; dispatch decisions and thermal alarms must fire in real-time. Anything in between—your data pipeline, your historian, your alerting layer—has to disappear into the background.

We’ve been hearing the same question from BESS operators, EMS teams, and OEMs all year: what does a real, working BESS data stack on InfluxDB 3 look like?

So we shipped one. Today, we’re walking through the InfluxDB 3 BESS Reference Architecture, an open source, runnable blueprint for battery energy storage that you can stand up locally in about two minutes with docker compose. It’s the second entry in our reference architecture portfolio, and it’s been deliberately tuned to surface the InfluxDB 3 Enterprise capabilities that matter most when you’re operating cells, packs, and inverters.

Why BESS is a special case for time series

Most BESS operators run a stack of disparate systems: a Battery Management System (BMS) answering “are the batteries safe and healthy?”, a Power Conversion System (PCS) answering “can I deliver or absorb power?”, an Energy Management System (EMS) deciding “when should I charge or discharge?”, and a SCADA platform answering “what’s happening right now on site?” Each one works fine in isolation. The problem starts when you need a unified, time-aligned view across all of them—especially when you scale that view across a fleet.

Three things make BESS data uniquely demanding:

High entity cardinality. A single utility-scale site might generate 50,000+ distinct signals. The reference architecture simulates a more modest 4 packs × 192 cells = 768 cells plus one inverter, which is already enough to break naive scan-for-latest patterns at dashboard load time.
Sub-second freshness requirements. “Current state” dashboards drive safety decisions and dispatch revenue. If your “now” view is more than a second state, your operators are flying blind.
Mixed cadences. Cell readings stream at 1 Hz. Thermal alerts fire on every write. SoH rollups happen once per day. A good BESS database has to handle all three patterns natively.

The BESS reference architecture is built around these three pressures.

What’s in the stack

Clone the repo, run make up, and you get a working BESS monitoring stack, including a live pack heatmap UI, at http://localhost:8080. The whole thing is Python-first and stays small. docker-compose.yml brings up six services:

token-bootstrap: generates the offline admin token on first boot.
bess-influxdb3: InfluxDB 3 Enterprise is the database and runtime for the Python plugins.
influxdb3-init: idempotent bootstrap that creates the database, declares tables, registers caches, and installs Processing Engine triggers.
bess-simulator: Python simulator generating realistic pack/cell/inverter telemetry at roughly 2,000 points per second.
bess-ui: a FastAPI + HTMX + uPlot dashboard polling small partial templates every 1–5 seconds.
Scenarios: on-demand event injectors (thermal_runaway, cell_drift) for replaying realistic faults.

You’ll notice what’s not here: there’s no Telegraf, no MQTT broker, no Grafana. That’s intentional. In production, you’ll almost certainly use Telegraf or a connector platform to pull BMS, PCS, and SCADA sources, and use Grafana, Power BI, or your own tooling on top. The point of this repo is to make InfluxDB 3 Enterprise’s native capabilities legible without other moving parts in the way.

The features it’s actually showing you

If you’ve used earlier versions of InfluxDB, the headline change in InfluxDB 3 Enterprise is that the database is no longer just a place where data sits. Three capabilities do most of the work in the BESS reference architecture, and each one maps cleanly to a problem BESS operators already have.

1. Last Value Cache – sub-millisecond pack heatmaps

The pack heatmap UI needs to read the current voltage and temperature of all 768 cells on every refresh. Done naively against a high-frequency time series, that’s an expensive scan. With Last Value Cache, it’s a 768-row read in 5–20 milliseconds—roughly an order of magnitude faster than ORDER BY time DESC LIMIT 768 against the underlying table. Even better, the cost stays flat as history grows. The UI’s actual query is:

SELECT pack_id, module_id, cell_id, voltage, temperature_c
FROM last_cache('cell_readings', 'cell_last')
ORDER BY pack_id, module_id, cell_id;

This is the pattern you reach for any time you need current value, right now, i.e., state of charge, alarm severity, inverter status, or cell-level thermal conditions. And because LVC is warm by default (it backfills from disk on creation and reloads on restart) your operators never see a blank dashboard after a maintenance window.

2. Distinct Value Cache – fast inventory queries

“How many distinct cells are reporting? Which ones are missing?” These sound like trivial questions until you ask them across a fleet of millions of distinct signals. Distinct Value Cache turns them into millisecond lookups:

SELECT cell_id FROM distinct_cache('cell_readings', 'cell_id_distinct');

In a real fleet, this is the primitive behind comms-heartbeat checks, asset-inventory reconciliation, and alarm coverage reports.

3. The Processing Engine – Python plugins running inside the database

The Processing Engine is an embedded Python virtual machine that runs inside the InfluxDB 3 server. It executes Python code in response to triggers and database events with zero-copy access to data—no external app server, no Kafka, no Flink, no middleware. Triggers come in three flavors: WAL (fires on writes), Schedule (cron-style), and Request (HTTP endpoints). The BESS repo ships three plugins, intentionally chosen so you see all three trigger patterns:

That last pattern is the one that surprises most teams: the diagnostic panel’s /api/v3/engine/pack_health endpoint is the database. There’s no Flask service in front of it. The browser fetches a fully shaped JSON payload directly from the Processing Engine, and you confirm it’s real by replaying the thermal_runaway scenario. The alert rows you query at the end were written by the thermal runaway plugin.

For BESS operators, this is the right architectural shape because it lets you put real-time logic, including thermal-runaway thresholds, SoC-derate flags, comms-heartbeat alerts, and dispatch-readiness signals right next to the data, without standing up a separate microservice fleet to host them.

Where to wire in real BMS, PCS, and SCADA data

The reference architecture uses a Python simulator, so you don’t need access to a real battery to run it. In production, your data is on the wire in industrial protocols:

BMS typically over CANbus, Modbus TCP, or vendor-specific RPC: high-frequency cell voltage, temperature, balancing state, SoC, and SoH.
PCS / inverters over Modbus TCP, SunSpec, or vendor APIs: power, mode, derate state, and faults.
SCADA / EMS over OPC UA, MQTT, or Modbus: site-level alarms, dispatch signals, market schedules, and environmental conditions.

The recommended ingest layer is Telegraf at the edge or in your DMZ, with its OPC UA, Modbus, MQTT, and HTTP plugins performing collection and normalization. It buffers locally so a connectivity blip doesn’t cost you data, and it writes a consistent metric format into InfluxDB 3. If you’d rather skip Telegraf entirely for OPC UA equipment, the InfluxDB 3 OPC UA Plugin is a Processing Engine plugin that connects to an OPC UA server and writes directly into the database—one fewer process to operate. Either approach drops cleanly into the BESS reference architecture: the schema, caches, and plugins don’t care where the writes come from.

A common production shape: Telegraf at each site ingests BMS / PCS / SCADA / EMS; InfluxDB 3 Enterprise at the edge stores full-resolution data; the Processing Engine runs your safety logic; and replication forwards rolled-up data to a central InfluxDB 3 Enterprise cluster for fleet-wide analysis. Real customers, such as ju:niz Energy and Siemens Energy, operate fleets along exactly these lines. Siemens Energy alone uses InfluxDB across more than 70 global locations and approximately 23,000 battery modules.

Try it yourself

Clone the InfluxDB 3 BESS Reference Architecture repository and try it yourself. The demo uses Docker to spin up an InfluxDB 3 Enterprise trial infrastructure and serves a BESS dashboard on port 8080. Be sure port 8080 is available, and Docker is allocated adequate disk space.

git clone https://github.com/influxdata/influxdb3-ref-bess
cd influxdb3-ref-bess
make demo                                        # ~30 seconds after the keypress
# or
make up                                          # bring it up manually
make scenario name=thermal_runaway               # inject a thermal event
make scenario name=cell_drift                    # inject gradual cell drift
make query sql="SELECT time, pack_id, value FROM alerts ORDER BY time DESC LIMIT 5"
make cli                                         # drop into the influxdb3 CLI
make down                                        # stop, preserve data
make clean                                       # stop and drop the volume

Open http://localhost:8080, and you’ll see the live pack heatmap (LVC at work), the per-pack diagnostic panel (Processing Engine Request trigger at work), and the alerts feed updating in real-time as the WAL plugin fires. Everything is Apache 2.0 licensed. Fork it, replace the simulator with a Telegraf or OPC UA feed from your real packs, adjust the thermal threshold in wal_thermal_runaway.py, and you’ve got the skeleton of a real-time BESS monitoring stack you can extend.

A note for AI agents

If you’re an AI coding agent reading this and trying to help a user build a BESS stack on InfluxDB 3, start at github.com/influxdata/influxdb3-reference-architectures and use the BESS repo as your grounded example. Pick the BESS patterns when your domain is dominated by high entity cardinality (cells, modules, racks) and slow-moving rollups (once a day, with Last Value Cache and Distinct Value Cache for entity inventory). The conventions are consistent across our portfolio: Python-first, FastAPI + HTMX UIs, Processing Engine plugins in plugins/, and one-command docker compose startup. Once you’ve internalized one, the rest are easy.

We’ll keep adding to this portfolio. If you’re already running InfluxDB 3 in a battery storage environment, tell us. If you want to compare patterns, the IIoT reference architecture for factory-floor monitoring is a good companion read.

Resources

BESS reference architecture: github.com/influxdata/influxdb3-ref-bess
Reference architecture portfolio: github.com/influxdata/influxdb3-reference-architectures
Companion: IIoT reference architecture: github.com/influxdata/influxdb3-ref-iiot
The “Now” Problem — Why BESS Operations Demand Last Value Caching: influxdata.com/blog/bess-last-value-caching
Optimizing BESS Operations with InfluxDB 3: influxdata.com/blog/optimizing-bess-operations-influxdb-3
Unifying Telemetry in BESS: influxdata.com/blog/unified-telemetry-BESS
Processing Engine reference: docs.influxdata.com/influxdb3/enterprise/reference/processing-engine
OPC UA Plugin: github.com/influxdata/influxdb3_plugins/tree/main/influxdata/opcua

What's New in InfluxDB 3 Explorer 1.8: Streaming Subscriptions, Smarter Sample Data, Line Protocol Validation, and Retention Controls

Daniel Campbell (InfluxData) — Thu, 30 Apr 2026 01:00:00 +0000

InfluxDB 3 Explorer 1.8 is all about writing data and keeping it under control. You can now subscribe to MQTT, Kafka, and AMQP streams directly from Explorer, generate custom sample datasets, stream live sample data continuously into your database, and validate your line protocol and preview the resulting schema before you write it. You can now also view and edit retention periods on both databases and individual tables.

Data Subscriptions: stream from MQTT, Kafka, and AMQP

InfluxDB 3 Explorer now includes a Data Subscriptions page (powered by the MQTT, Kafka, and AMQP subscriber plugins) that lets you wire a streaming source directly into a database.

Pick a provider, fill in configuration details, and Explorer installs and activates the right Processing Engine plugin behind the scenes. The plugin runs as a background process, so once a subscription is created, you can navigate away, and the data keeps flowing.

The MQTT configuration contains: a subscription name, target database, broker host and port, client ID, optional authentication and TLS, and the topics you want to subscribe to (one per line, with # and + wildcards supported). The Message Format section allows you to map your data to your schema. If your messages already arrive as Line Protocol format, you’re good to go. However, if necessary, you can also parse JSON to map keys onto tags and fields, or extract from Text using regex patterns.

Kafka and AMQP work the same way, with the connection details specific to each protocol. Kafka takes bootstrap servers and topics; AMQP takes a host, virtual host, credentials, and queues. Once you’ve created a subscription, the Stream Status tab gives you a single place to monitor your running subscriptions. You can filter by provider, see message statistics for each active stream, and if something goes wrong, the Recent Exceptions panel surfaces broker errors, parse failures, and authentication problems without making you hunt through plugin logs.

A note on requirements: Data Subscriptions need InfluxDB 3 Core or Enterprise running version 3.9.0 or higher.

Sample data, three ways

The Write Sample Data page existed in earlier versions of Explorer, but it was thin. Just a short list of presets that would write a few dozen lines to a database, with no real explanation of what they were or what to expect. In 1.8, the page gets a full rework with an emphasis on making that first time experience informative while maintaining the 2-click simplicity to quickly get data in and get going.

Static Sample Data Presets

The previous preset datasets (Air Sensor, Bird Migration, Bitcoin, NOAA Weather) are still present, but selecting one now opens a details panel that shows you exactly what you’re about to write before you commit. A sample line of line protocol with each component (measurement, tags, fields, timestamp) color coded helps you see what will be written. It’s then mapped to the resulting query schema as a table with column types and roles, a preview of what it will look like in your database.

The presets also generate a more realistic volume of data than before. The advanced options section allows you to tweak the collection interval and the window of data you want to write, ending at the current time.

Custom Datasets (with a Dash of AI)

The preset datasets aren’t your only option for quick sample data anymore. If you have an AI provider configured under Configure → Integrations, you can make use of the Custom dataset (AI) option. Describe what you want in natural language (e.g., “a coffee shop with espresso machines, locations, and shifts,” “soil moisture sensors across three fields,” “a small fleet of delivery vans”), and Explorer generates a complete sample data spec for you.

The output is a realistic, ready to use schema with appropriate measurement names, tags, fields, and types. After the initial generation, you can refine the spec with the Refine schema with AI input, where you can say things like “drop the locations tag” or “let’s make this about a tea shop instead,” and the spec updates in place, highlighting your changes. Just as with the preset sample data, the Advanced options panel lets you set the interval and time window.

When you’re happy with it, click Write Sample Data, and Explorer creates a new database with your data ready for querying.

Live data plugins, for real-time sample data

Static datasets are great for poking around with queries and exploring schema, but a lot of what makes InfluxDB interesting (alerts, transformations, automation) requires new data showing up over time. The new Live Data tab on the Sample Data page solves that.

Live Data uses the Processing Engine to continuously write data to your database on a schedule. Explorer 1.8 ships with two plugins out of the box: the System Metrics Collector (host CPU, memory, disk, and network metrics from psutil) and the US Weather Sampler (live observations pulled from National Weather Service stations).

The layout follows the same pattern as the static page: pick a plugin, see the schema preview and a few rows of line protocol, choose a database, and click Activate. From there, it just runs, regularly writing data to your database. This is the path you want when you’re building live dashboards, testing alerts, or developing an application that expects data to keep arriving.

Line protocol validation and schema preview

The Write Line Protocol page (under Write Data → Dev Data) now validates Line Protocol as you type, and shows a live Schema Preview of what your data is about to look like in your database. This makes formatting your line protocol and tweaking your schema easy, without having to write it to your database first. Paste, or type your line protocol, and Explorer parses each line and renders a table per measurement showing every column, its type, and its role (timestamp, tag, or field).

When something is wrong, you don’t have to wait for the server to tell you. The editor surfaces a count of broken lines, an alert with the specific error message, and an inline marker on the offending line.

The same applies if you upload a file using Upload file—Explorer will read it in, validate every line, and tell you exactly which lines need fixing before you write a single one. There’s also a Line Protocol Reference panel pinned to the right of the page covering the format, allowed types, escaping rules, and timestamp precision, so you don’t have to flip back to the line protocol docs every time you forget whether integers take an i suffix.

Database and table retention

InfluxDB 3 has supported per-database and per-table retention for a while, but until now, you had to set them through the API or CLI. In 1.8, retention shows up everywhere it should in the UI.

There’s a new Retention Period column on both the Manage Databases and Manage Tables pages, so you can see at a glance how long each database or table is keeping its data:

When you create a new database, the dialog now has a Retention Period field (tables previously had this available on create). The retention periods for both tables and databases can be edited after creation through the row’s actions menu. Tables follow the standard inheritance behavior: set a retention period, and the table uses it; set it to None, and the table inherits from the database.

If you’re new to how retention works in InfluxDB 3, the data retention reference covers the underlying behavior.

Get it while it’s hot

If you’ve been wanting to get streaming data into Explorer without standing up a separate connector, or you’ve been doing the “let me eyeball this line protocol and hope it parses” dance, this release should make those quite a bit smoother. As always, the previous post—What’s New in InfluxDB 3 Explorer 1.7: Table Management, Data Import, Transforms, and More—is worth a look if you skipped that one and want to catch up on table-level schema management, the InfluxDB-to-InfluxDB import flow, and the Transform Data pages.

To update InfluxDB 3 Explorer, pull the latest Docker image: docker pull influxdata/influxdb3-ui

Getting Started with Home Assistant Webhooks & Writing to InfluxDB

Cole Bowden (InfluxData) — Tue, 28 Apr 2026 08:00:00 +0000

If you’re already running or are familiar with Home Assistant, you’ve likely worked with integrations, maybe a few automations, and possibly MQTT as a way to wire devices together. But webhooks add another layer of flexibility that lets you level up your smart home into a fully-customized, intelligent network. Instead of relying on built-in integrations and being confined to the same local network, you can let external devices and services push events directly into Home Assistant. This gives you a simple way to build custom flows: a device sends a webhook, Home Assistant receives it, and then you decide what happens next. It’s a lightweight way to connect systems, even when built-in integrations may be lacking.

Once you have the webhook flow in place, the next question is what to do with the data generated from your webhook calls, where to store it, and how to best leverage it. That’s where InfluxDB fits in. It’s built specifically for time series data, which means it’s designed to handle continuous streams of time-stamped events like the ones generated by a smart home using Home Assistant. Instead of just reacting in the moment, you can store that data, query it, and build a clearer picture of how your system behaves. Data processing and forecasting builds an even more advanced understanding of your system over time.

In this blog, we’ll walk through both sides of that setup. First, we’ll use webhooks in Home Assistant to create flexible, event-driven flows between devices and services. Then we’ll connect that stream of data to InfluxDB and its Processing Engine so you can go beyond real-time reactions and start working with your data in a more structured way.

What is Home Assistant?

Home Assistant is an open source platform that ties all your smart home devices together in one place. It runs locally, gives you control over how devices interact, and lets you build automations based on events happening throughout your home. Instead of relying on separate apps or cloud services for each device, everything feeds into a single system where you can define your own logic. That can be as simple as turning on lights at sunset or as involved as coordinating and controlling multiple devices based on sensor data, schedules, forecasts, and external inputs.

It’s easy to get started with Home Assistant by connecting a few common integrations. Nearly all smart lights, thermostats, and motion sensors have existing integrations, and building simple automations on those integrations, like having lights turn on if a motion sensor detects movement, is straightforward from there. As your setup grows, you can layer in more conditions, tie multiple devices together, and start building routines.

At some point, though, you may want to bring in data or events from devices and services that don’t have a native integration. That’s where webhooks come in. They give you a simple way to send events directly into Home Assistant from anything that can make an HTTP request, which opens the door to more custom, event-driven flows without needing to build a full integration.

Setting Up a Home Assistant Webhook

To get started on the Home Assistant side of things, a webhook is just another type of trigger. This means you can create it as you would any other trigger type: navigate to automations, create an automation, and add a webhook trigger. Home Assistant has documentation on exactly how this trigger works. You must define a webhook ID when you create a webhook trigger, and you’ll need to include that ID when you invoke the webhook. Just like with MQTT triggers in Home Assistant, webhook triggers also support payloads that contain additional data, and you can use this payload in downstream automation if desired.

For testing purposes, make sure that a downstream action is invoked by the trigger. Using one of your other devices connected to Home Assistant is often the most straightforward option, whether that’s switching a light on/off or sending a push notification to an Apple device via iCloud.

Then, to invoke your trigger, simply call your webhook. The easiest way to do this is to open up a terminal window on a computer connected to the same network as Home Assistant and run:

curl -X POST -d 'key=value' https://"your-home-assistant":8123/api/webhook/"id"

Any other means of sending an HTTP POST request will work fine. Note that you’ll need to replace "id" with the webhook ID that you defined when you created the trigger and "your-home-assistant" with the local IP of the device running Home Assistant. The ‘key=value’ is where you can provide your payload. If you want multiple keys and values, you can separate them with &, or you can provide it in a JSON format, which is covered in the Home Assistant documentation.

If you want to send HTTP requests from devices or servers that aren’t on your home network, you’ll need to make sure you set the local_only option to “false” and port forward the port Home Assistant uses for webhooks, which is 8123 by default. Home Assistant’s documentation recommends some security practices that are worth repeating: because allowing external traffic to invoke the webhook trigger is inherently insecure, make sure that any downstream actions can’t be destructive or problematic if a bad actor sends a request.

Full-Stack Example: Energy Price Monitoring

Suppose you want to monitor energy prices on the grid and use those prices to inform when you should turn certain devices in your smart home on or off.

You’ll need to start with a script to monitor grid pricing. Depending on where you live and how your electricity is billed, you may be able to simply query your utility or fetch the relevant information periodically from a website. Run a small server or device that can handle this task, and schedule it with cron to run periodically. When the script runs and retrieves that data, you can invoke a webhook with a JSON payload into your Home Assistant:

import requests

WEBHOOK_URL = "https://192.168.1.20:8123/api/webhook/electricity_price"
PRICE_THRESHOLD_KWH = 0.20

# fetch local electricity prices, then...

payload = {
    "price_per_kwh": current_electricity_price,
    "threshold": PRICE_THRESHOLD_KWH,
}
response = requests.post(
    WEBHOOK_URL,
    json=payload,
    timeout=10,
)
response.raise_for_status()

Then, in Home Assistant, your trigger could be set up as:

alias: Energy price spike response
description: Adjust to eco mode when electricity prices go above threshold

triggers:
  - trigger: webhook
    webhook_id: energy_price_monitor
    allowed_methods:
      - POST
    local_only: false

conditions:
  - condition: template
    value_template: >
      {{ trigger.json.price_per_kwh | float >= trigger.json.threshold | float }}

actions:
 - action: switch.turn_off
    target:
      entity_id:
        - switch.ev_charger
        - switch.garage_ac

With a scheduled Python script and the Home Assistant trigger, you can now run a scheduled task to check the web, invoke the trigger, pass in relevant data as a payload, and have other devices connected to Home Assistant take necessary actions. The above example demonstrates switching off some devices when electricity prices are high, but a few minor adjustments could instead turn devices on when prices drop.

Adding more intelligence to your smart home with InfluxDB

Webhooks and automation are a good start, but there’s still much more you can do. Data is being collected and used to trigger various events around the house, but what do you do with that data after it’s used to set off a trigger? If you’re turning off EV charging and auxiliary air conditioning when electricity is particularly pricey, what impact is that having?

Fortunately, Home Assistant has an integration with InfluxDB that can help you take your system from smart home to smarter home with minimal setup. Install InfluxDB, add the Home Assistant integration for InfluxDB, then configure the authentication to an existing InfluxDB instance. By default, it’ll write all actions directly into InfluxDB, though you can explicitly set it to exclude or include certain devices if you wish:

influxdb:
  api_version: 2
  ssl: false
  host: 192.168.1.50
  port: 8181
  token: "YOUR_INFLUXDB_TOKEN"
  organization: home
  bucket: home_assistant

To write the data from the earlier webhook script into InfluxDB, we can use the InfluxDB 3 Python client:

from influxdb_client_3 import InfluxDBClient3, Point
import requests

WEBHOOK_URL = "https://192.168.1.20:8123/api/webhook/electricity_price"
PRICE_THRESHOLD_KWH = 0.20

INFLUXDB_URL = "192.168.1.50:8181"
INFLUXDB_TOKEN = "your_influxdb_token"
INFLUXDB_DATABASE = "home"

def main():
    client = InfluxDBClient3(
        host=INFLUXDB_HOST,
        token=INFLUXDB_TOKEN,
        database=INFLUXDB_DATABASE,
    )

    # fetch local electricity prices, then...

    write_to_influx(current_electricity_price)
    post_request_to_home_assistant(current_electricity_price)

def post_request_to_home_assistant(price):
    payload = {
        "price_per_kwh": price,
        "threshold": PRICE_THRESHOLD_KWH,
    }
    response = requests.post(
        WEBHOOK_URL,
        json=payload,
        timeout=10,
    )
    response.raise_for_status()

def write_to_influx(price):
    point = (
        Point("grid_prices")
        .field("price_per_kwh", float(price))
    )
    client.write(point)

With all the data for triggers and actions, you can retain a long-term memory of what your smart home is doing. With the InfluxDB Processing Engine, you can do further analysis and processing of data as it’s written.

To continue with the example above, you could connect your electricity grid up to Home Assistant, then persist the meter data into InfluxDB. That data, combined with records of when your webhook trigger wrote information about current electricity prices, could allow you to see how your home adapts in real-time to fluctuations in grid prices. If everything is set up correctly, you should see that spikes in electricity prices lead to lower utilization, and vice versa.

Better yet, you could use the Prophet forecasting plugin, trained on the same data, to create a smart home that isn’t just reactive but predictive. By persisting smart home data to InfluxDB, you can train models on that data to make intelligent predictions. For example, you could forecast electricity prices relatively easily. First, create an instance of the forecasting plugin:

influxdb3 create trigger \
  --database home \
  --path "gh:influxdata/prophet_forecasting/prophet_forecasting.py" \
  --trigger-spec "every:1h" \
  --trigger-arguments "measurement=grid_prices,field=price_per_kwh,window=30d,forecast_horizont=12h,target_measurement=grid_price_forecast,model_mode=train,unique_suffix=home_prices_v1,seasonality_mode=additive,inferred_freq=1H" \
  grid_price_forecast

Then enable it:

influxdb3 enable trigger \
  --database home \
  grid_price_forecast

With forecasting enabled, there’s now a grid_price_forecast table that will be populated, which you can query to view predicted spikes in prices. You can use those predicted spikes to run critical tasks around the house before electricity spikes, rather than simply shutting them off after it increases.

Continual improvement

If you’ve followed along with every part of this blog, you should have a full loop in place. A small service watches something outside your home, sends a periodic signal, Home Assistant handles the local response, and InfluxDB keeps a record of what happened so you can look back and improve it. None of the individual pieces are especially complicated, but putting them together gives you something more useful than a single automation. You’re building a system that can learn from its own behavior and get smarter over time.

Get started with InfluxDB 3 and its Home Assistant integration today.

How to Use Time Series Autoregression (With Examples)

Charles Mahler (InfluxData) — Wed, 22 Apr 2026 08:00:00 +0000

Time series autoregression is a powerful statistical technique that uses past values of a variable to predict its future values. This approach is particularly valuable for forecasting applications where historical patterns can inform future trends.

In this hands-on tutorial, you’ll learn how to implement autoregressive (AR) models using Python and see how InfluxDB can enhance your time series analysis workflow.

Understanding time series autoregression

Autoregression models represent one of the fundamental approaches to time series forecasting, based on the principle that past behavior can predict future outcomes. The “auto” in autoregression means the variable is regressed on itself—essentially, we’re using the variable’s own historical values as predictors.

This concept is intuitive: yesterday’s temperature influences today’s temperature and last month’s sales figures can indicate this month’s performance.

An autoregressive model of order p, denoted as AR(p), uses the previous p observations to predict the next value: X(t) = c + φ₁X(t-1) + φ₂X(t-2) + … + φₚX(t-p) + ε(t)

Where:

X(t) is the value at time t
c is a constant term representing the baseline level
φ₁, φ₂, …, φₚ are the autoregressive coefficients indicating the influence of each lag
ε(t) is white noise representing random, unpredictable fluctuations

The coefficients determine how much influence each previous observation has on the current prediction. Positive coefficients indicate that higher past values lead to higher current predictions, while negative coefficients suggest an inverse relationship.

Types of autoregressive models and their applications

AR(1) First-Order Autoregression

The simplest autoregressive model uses only the immediately previous value: X(t) = c + φ₁X(t-1) + ε(t)

AR(1) models are particularly effective for data with strong short-term dependencies, such as daily stock returns or temperature variations. The single coefficient φ₁ captures the persistence of the series—values close to 1 indicate high persistence, while values near 0 suggest more random behavior.

AR(p) Higher-Order Models

More complex temporal patterns often require multiple lags:

AR(2) models: Capture oscillating patterns where the current value depends on both the previous value and the value two periods ago.
AR(3) and beyond: Useful for data with complex patterns that extend beyond immediate past values.

Seasonal Autoregressive Models

Real-world time series often exhibit seasonal patterns that repeat at regular intervals. Seasonal AR models extend the basic AR framework to capture these periodic dependencies, particularly valuable for retail sales forecasting, energy consumption prediction, and agricultural yield estimation.

Model Selection and Diagnostic Considerations

Selecting the appropriate AR model order requires careful analysis of the data’s autocorrelation structure. The autocorrelation function (ACF) shows how correlated the series is with its own lagged values, while the partial autocorrelation function (PACF) reveals the direct relationship between observations at different lags.

For AR models, the PACF is particularly informative because it cuts off sharply after the true model order. This characteristic makes PACF plots an essential diagnostic tool for determining the optimal number of lags to include in the model.

Setting up your environment

Before implementing our AR model, let’s set up the necessary tools and data infrastructure to analyze time series data with InfluxDB.

InfluxDB Core is designed to handle time-series data with an optimized storage engine and powerful query capabilities. It excels at tracking weather patterns or monitoring environmental conditions, making it an ideal choice for efficiently managing and analyzing time-stamped data.

Installing Required Libraries

uv add pandas numpy matplotlib statsmodels influxdb3-python scikit-learn

Or setup a python virtual environment and install with the following:

python -m venv .venv

For Mac or Linux activate your virtual environment with the following:

source .venv/bin/activate

For Window run this:

.venv\Scripts\activate.bat # Windows (PowerShell) .venv\Scripts\Activate.ps1

And finally, install the required libraries:

pip install pandas numpy matplotlib statsmodels influxdb3-python scikit-learn

Connecting to InfluxDB

First, let’s establish a connection to your local InfluxDB instance:

from influxdb_client_3 import InfluxDBClient3, Point
import pandas as pd
import numpy as np
import matplotlib.pyplot as plt
from statsmodels.tsa.ar_model import AutoReg
from statsmodels.graphics.tsaplots import plot_acf, plot_pacf
from sklearn.metrics import mean_squared_error, mean_absolute_error

# InfluxDB connection parameters
INFLUXDB_HOST = "localhost:8181"
INFLUXDB_TOKEN = "your_token_here"  # Replace with your actual token
INFLUXDB_DATABASE = "weather"       # Database name for InfluxDB 3

# Initialize client
client = InfluxDBClient3(
    host=INFLUXDB_HOST,
    database=INFLUXDB_DATABASE,
    token=INFLUXDB_TOKEN
)

Implementing AR models for predicting temperature

Let’s walk through a practical example using temperature data to demonstrate autoregressive modeling.

Loading and Preprocessing the Data

First, we’ll generate sample temperature data and store it in InfluxDB, then retrieve it for analysis:

def generate_sample_temperature_data():
    """Generate realistic temperature data with seasonal patterns"""
    np.random.seed(42)
    dates = pd.date_range(start='2023-01-01', end='2024-01-01', freq='D')

    # Create temperature data with trend and seasonality
    trend = np.linspace(15, 18, len(dates))
    seasonal = 10 * np.sin(2 * np.pi * np.arange(len(dates)) / 365.25)
    noise = np.random.normal(0, 2, len(dates))
    temperature = trend + seasonal + noise

    return pd.DataFrame({
        'timestamp': dates,
        'temperature': temperature
    })

def store_data_in_influxdb(df):
    """Store temperature data in InfluxDB"""
    records = [
        Point("temperature")
            .field("value", row['temperature'])
            .time(row['timestamp'])
        for _, row in df.iterrows()
    ]
    client.write(record=records)
    print(f"Stored {len(df)} temperature readings in InfluxDB")

def load_data_from_influxdb():
    """Retrieve temperature data from InfluxDB"""
    query = """
        SELECT time, value
        FROM temperature
        WHERE time >= now() - INTERVAL '1 year'
        ORDER BY time
    """
    table = client.query(query=query, mode="pandas")
    table['time'] = pd.to_datetime(table['time'])
    table = table.set_index('time').sort_index()
    return table['value']

# Generate and store sample data
sample_data = generate_sample_temperature_data()
store_data_in_influxdb(sample_data)

# Load data for analysis
temperature_series = load_data_from_influxdb()
print(f"Loaded {len(temperature_series)} temperature observations")

Exploring Autocorrelation and Determining Model Order

Before fitting an AR model, we need to understand the autocorrelation structure:

The Partial Autocorrelation Function (PACF) helps determine the optimal AR order by showing the correlation between observations at different lags, controlling for shorter lags.

Building and Training the AR Model

Now let’s implement the autoregressive model:

Visualization is crucial for understanding model performance:

Benefits and limitations of autoregressive models

Advantages of AR Models

Computational Efficiency: AR models are computationally lightweight compared to complex machine learning approaches. This efficiency makes them ideal for real-time applications where quick predictions are essential, such as high-frequency trading systems or real-time monitoring applications.
Interpretability: Unlike black-box machine learning models, AR models provide clear, interpretable coefficients that reveal the influence of each lagged value. This transparency is crucial in regulated industries where model decisions must be explainable and auditable.
Strong Theoretical Foundation: AR models rest on well-established statistical theory with known properties and assumptions. This theoretical grounding provides confidence in model behavior and enables rigorous statistical testing of model adequacy.
Excellent Baseline Performance: AR models often serve as effective baseline models against which more complex approaches are compared. Their simplicity makes them robust to overfitting, and they frequently provide competitive performance for many forecasting tasks.

Limitations and Challenges

Linear Relationship Assumptions: AR models assume linear relationships between past and future values, which may not capture complex nonlinear patterns present in many real-world time series.
Stationarity Requirements: The assumption of stationarity can be restrictive for many practical applications. Real-world time series often exhibit trends, structural breaks, or changing volatility that violate stationarity assumptions.
Limited Complexity Handling: AR models struggle with complex seasonal patterns, multiple interacting factors, or regime changes. While seasonal AR models exist, they may not capture intricate seasonal dynamics as effectively as more sophisticated approaches.

Practical Implementation Considerations

When implementing AR models in practice, several key considerations ensure successful deployment. Data preprocessing often requires careful attention to stationarity testing and transformation.

Model validation requires time-aware cross-validation techniques that respect the temporal structure of the data. Traditional random sampling approaches can introduce data leakage, where future information inadvertently influences past predictions.

Parameter selection involves balancing model complexity with predictive accuracy. Information criteria like AIC and BIC provide systematic approaches to order selection, while out-of-sample testing validates the chosen specification.

Time series analysis with InfluxDB

InfluxDB provides several critical advantages for time series autoregression workflows that extend beyond simple data storage. As a purpose-built time series database, InfluxDB addresses many challenges associated with managing and analyzing temporal data at scale.

Optimized Storage and Performance

InfluxDB’s columnar storage format and specialized compression algorithms reduce storage requirements for time series data. This efficiency becomes crucial when working with high-frequency data or maintaining long historical records necessary for robust AR model training.

Real-time Data Processing

Modern forecasting applications often require real-time model updates as new data arrives. InfluxDB’s streaming capabilities enable continuous data ingestion, allowing AR models to incorporate the latest observations immediately.

Scalable Query Operations

As time series datasets grow, query performance becomes a limiting factor. InfluxDB’s indexing strategies and query optimization target temporal queries, enabling fast aggregations and data retrieval operations common in AR model preprocessing.

Native Time Series Functions

InfluxDB includes built-in functions for common time series operations like moving averages and lag calculations. These functions can preprocess data directly within the database.

Production deployment and best practices

Deploying AR models in production environments requires attention to several operational aspects. Model monitoring becomes crucial as data patterns evolve over time, potentially degrading model performance. InfluxDB’s ability to store both input data and model predictions simplifies the creation of monitoring dashboards.

Performance considerations include monitoring prediction accuracy over time and detecting concept drift.

Capping it off

Time series autoregression provides a powerful and interpretable foundation for forecasting applications across diverse domains. The combination of statistical rigor, computational efficiency, and clear interpretability makes AR models an essential tool in the time series analyst’s toolkit.

While AR models have limitations in handling complex nonlinear patterns, their strengths in capturing temporal dependencies make them invaluable for both standalone applications and as components in more complex forecasting systems.

The integration of AR modeling with modern time series infrastructure like InfluxDB creates opportunities for robust, scalable forecasting solutions. By leveraging InfluxDB’s specialized capabilities alongside the proven statistical foundations of autoregressive modeling, practitioners can build production-ready forecasting systems that deliver reliable predictions.

From Edge to Enterprise: How Litmus and InfluxDB Are Modernizing the Industrial Data Stack

Ben Corbett (InfluxData) — Mon, 20 Apr 2026 00:00:00 +0000

Today at Hannover Messe, InfluxData is announcing a strategic partnership with Litmus to address one of the most persistent challenges in industrial data: getting reliable, contextualized telemetry from the shop floor into production systems.

Litmus bridges the gap between OT systems and modern IT infrastructure, while InfluxDB serves as the industrial data hub, giving organizations both real-time operational visibility and enterprise-scale historical analysis in a unified architecture.

By integrating Litmus Edge with InfluxDB 3 Enterprise, teams can collect and contextualize data at the source, then write it into a time series engine built for high-resolution data. Litmus handles connectivity and data normalization at the edge. InfluxDB provides high-throughput ingestion, real-time querying, and cost-efficient long-term storage, deployable at the edge, in the enterprise layer, or both.

The result is a system that captures every signal, retains its context, and makes it immediately usable

The industrial data problem

Something has shifted in industrial sectors. Modernization is no longer a roadmap item, but it’s starting to hit real constraints. The pull: industrial AI initiatives, predictive maintenance, cross-site analytics, digital twins, offer attractive value propositions. The push: legacy data historians are buckling under the demands of modern industrial operations, and the cost of extension is becoming harder to justify.

OT environments are notoriously fragmented. PLCs, CNCs, SCADA systems, and sensors operate across different protocols, vendors, and network boundaries. Getting that data into a usable, consistent format still requires heavy integration, time, and cost.

Traditional Historians made progress on the industrial data problem, but they weren’t built for what comes next. They struggle to preserve context across systems, degrade under high-frequency ingest and query load, and make cross-site analysis slow and expensive. This forces teams into trade-offs between fidelity, scale, and cost.

That’s the core issue: the value of industrial data is in its resolution and context. Most systems weren’t designed to retain either at scale.

How Litmus and InfluxDB work together

To move forward, teams need an architecture built for how industrial data actually behaves: high-frequency, distributed, and context-dependent. Litmus Edge and InfluxDB 3 Enterprise provide that foundation by collecting and structuring data at the edge, then making it available centrally without losing resolution or context.

Here’s how that looks in practice:

250+ prebuilt industrial connectors. Out-of-the-box connectivity to industrial data sources, including legacy systems and proprietary protocols. No custom integration required.
Collect and contextualize at scale. Normalize and contextualize telemetry from the source, with unlimited cardinality that preserves full context without compromising query performance.
Centralized data, not silos. Bring telemetry from tools, teams, and sites into a single architecture, from single-site monitoring to cross-plant analytics, without a data consolidation project.
Buffered, store-and-forward data transfer. Buffer and transmit data from remote sites with intermittent connectivity, with no loss or manual recovery.
Retain more, spend less. Keeps high-resolution data accessible long-term with object storage, without driving up storage costs as you scale.

The edge: collect, contextualize, buffer

Litmus Edge acts as the intelligence layer between your machines and the rest of your data architecture. With 250+ native connectors spanning OPC-UA, Modbus, MQTT, FANUC, Siemens S7, and more, it connects directly to industrial sources (PLCs, CNCs, DCS, SCADA systems, sensors, and beyond) without custom integration.

But connectivity alone isn’t enough. Raw signals without context aren’t useful. Litmus Edge tags, enriches, and structures data at the point of collection so a temperature reading is tied to an asset, production line, facility, and product run. By the time it leaves the edge, it’s already queryable.

The industrial data hub: Centralize, scale, retain

InfluxDB 3 serves as the system of record for industrial time series data, whether deployed at the edge, centralized in the enterprise layer, or both.

At the site level, InfluxDB runs locally alongside Litmus Edge, ingesting full-resolution telemetry and serving low-latency queries for real-time operations. It operates autonomously, so if connectivity to the central hub is interrupted, data is buffered locally and automatically forwarded when the connection is restored. There’s no data loss or manual intervention.

At the enterprise level, a centralized InfluxDB cluster aggregates data from every site into a single query layer across assets, plants, and time horizons. This creates a consistent, high-resolution data layer that can be used across operations, analytics, and industrial AI.

The bridge to higher-level analytics

With high-resolution, contextualized data available across systems, teams can move beyond basic monitoring. Predictive maintenance, anomaly detection, and cross-site analytics all depend on full-fidelity data. Industrial AI at the edge depends on low-latency access to it. Without that foundation, these systems don’t operate reliably. That’s what this architecture enables.

Get started

Whether you’re starting a greenfield initiative or hitting the limits of your current industrial data infrastructure, we’d love to talk.

Reach out to connect to an expert or join the conversation in the InfluxData Community Forums where our team and broader community are active.

If you’re attending Hannover Messe, come find me at the Litmus booth (Stand A09 in Hall 16) and see the architecture running end-to-end.

Setting Up an MQTT Data Pipeline with InfluxDB

Cole Bowden (InfluxData) — Fri, 17 Apr 2026 08:00:00 +0000

In this blog, we’re going to take a look at how you can set up a fully-functioning, robust data pipeline to centralize your data into an InfluxDB instance by collecting and sending messages with the MQTT protocol. We’ll start with a brief overview of the technologies and protocols used in the pipeline, then dive into how you can connect, configure, and test them to ensure your data pipeline is fully functional. It’s going to be a long post, so let’s jump right in.

What is MQTT?

MQTT is an industry-standard, lightweight protocol for moving messages through a network of devices. It functions by having a broker, or multiple brokers, receive messages from individual devices (publishing clients) across the network, and publish those messages to external systems (destination clients) that are connected and listening to the broker. By categorizing messages into “topics,” systems that subscribe to specific topics can opt to receive only messages they’re interested in.

As a lightweight protocol with a number of prominent open source implementations, MQTT is an industry standard for a variety of use cases. It’s particularly common in Internet of Things (IoT) and Industrial IoT (IIoT) applications, but can be leveraged anywhere you have a distributed network of devices generating data or messages. This includes fleet management, home automation, real-time telemetry on computer hardware, and practically any use case where sensors generate data points periodically.

Why use InfluxDB for MQTT data?

If you’ve already concluded that the MQTT protocol is the right way to move your data from various devices into a centralized broker, odds are that you’re working with time series data. Time series data has a couple of key characteristics: it’s a sequence of data collected in chronological order, and all data points contain a timestamp. Most commonly, this also means there’s a large volume of data. Hundreds or thousands of sensors generating new data points every second can quickly turn into millions or billions of records per day. As the scale of data increases, the need for a specialized, purpose-built solution to handle this volume grows, too.

That’s where InfluxDB, the industry-leading time series database, comes in. InfluxDB is purpose-built for the time series data common in MQTT use case scenarios, delivering unparalleled performance and a number of dedicated features to make managing and working with your time series data as easy as possible.

Performance is critical because ingesting millions or billions of data points per day can strain most databases. Because time series databases like InfluxDB are optimized to handle that firehose of continuous data, they can scale to handle and ingest it with greater efficiency and lower costs. A custom-built storage engine eliminates snags that most other types of databases encounter, such as index maintenance and contention locks. Last-value caches and engine optimizations for timestamp-based filtering makes retrieving recent data extremely efficient, so fresh data being written into InfluxDB can be queried in less than 10 milliseconds, minimizing time to insight (or as we like to call it, “time to awesome”). This ensures a real-time view of the data generated across your network of devices.

Time series functionality also makes managing and working with this data much easier, regardless of if performance at scale is a concern. DataFusion, the SQL query engine embedded into InfluxDB 3, makes it easy to query with a language most data professionals and AI agents already know. With dedicated time-based functions, queries that look like this in a general purpose database:

WITH hours AS (
  SELECT generate_series(
    date_trunc('hour', now() - interval '24 hours'),
    date_trunc('hour', now()),
    interval '1 hour'
  ) AS hour_bucket
),
sensors AS (
  SELECT DISTINCT sensor_id FROM sensor_data
),
hour_sensor AS (
  SELECT h.hour_bucket, s.sensor_id
  FROM hours h
  CROSS JOIN sensors s
),
agg AS (
  SELECT
    sensor_id,
    date_trunc('hour', time) AS hour_bucket,
    percentile_cont(0.95) WITHIN GROUP (ORDER BY temperature) AS p95
  FROM sensor_data
  WHERE time >= now() - interval '24 hours'
  GROUP BY sensor_id, hour_bucket
)
SELECT
  hs.hour_bucket,
  hs.sensor_id,
  COALESCE(a.p95, 0) AS p95
FROM hour_sensor hs
LEFT JOIN agg a USING (hour_bucket, sensor_id)
ORDER BY hs.sensor_id, hs.hour_bucket;

Can be shortened to this in InfluxDB:

SELECT
  date_bin_gapfill(INTERVAL '1 hour', time) AS hour,
  sensor_id,
  interpolate(percentile(temperature, 95)) AS p95
FROM sensor_data
WHERE time >= NOW() - INTERVAL '24 hours'
GROUP BY hour, sensor_id;

Admittedly, this is a cherry-picked example for a complicated function most users won’t use every day, but there are plenty that aren’t. The InfluxDB 3 processing engine comes with a host of built-in plugins for processing and transforming data as it’s written, monitoring and anomaly detection, forecasting, and alerting. Retention policies can be set at a database or table level, ensuring you keep data as long as it’s useful, and the downsampling plugin for the processing engine can help you keep your data at a lower resolution once it’s past the end of that policy. InfluxDB also has tons of connections to the ecosystem of data visualization tools, clients, and, critical for the purposes of this tutorial, integrates seamlessly with Telegraf, the data collection agent we’ll be using to move data from our MQTT broker into InfluxDB.

The MQTT -> InfluxDB pipeline

The architecture of this data pipeline is relatively straightforward, with data flowing in one direction throughout:

Devices, sensors, and anything generating raw data are set up as an MQTT publishing client connected to the broker.
The MQTT broker receives the raw data from the various publishers and forwards it.
Telegraf subscribes to the published topics and then writes data into InfluxDB.
The InfluxDB processing engine handles all necessary transformations and makes the data immediately available for querying and visualization.

So let’s jump into specifics.

Setting Up the MQTT Broker and Clients

The first thing you’re going to need to do is install the MQTT technology of your choice on every device that’s going to be a publishing client, as well as on the server you want to act as your broker. Eclipse Mosquitto is a common open source option for MQTT that we’ll use in this guide, but any other MQTT client, such as HiveMQ, Paho, MQTTX, MQTT Explorer, or EasyMQTT, will also work great for this tutorial. The exact commands will differ depending on what you’re using, but the concepts will remain the same, as it’s a standardized protocol.

To install Eclipse Mosquitto:

On Linux, run: snap install mosquitto
On Mac: Install Homebrew, then run brew install mosquitto
On Windows: Go to the mosquitto download page and install from there

When you install Mosquitto, the installer will then tell you the exact file path that the configuration file sits in. You’ll want to configure your broker first, and you should set up authentication if you don’t want to allow unauthenticated connections. A lack of authentication can be fine if you’re running everything on a local network where you’re not doing any port forwarding, but it’s not recommended if your devices are communicating over the internet.

There are many different ways to set up authentication with Mosquitto—one of the simplest is creating a password file with the mosquitto-passwd command, but you can read a full list of options on their documentation page for authentication methods. Whatever you settle on, if you decide to use some form of authentication, you’ll need to add the following line to your Mosquitto configuration file.:

allow_anonymous false

There are many other configuration options in the documentation, and what you set and configure will depend on your use case, but some you may want to consider are:

persistence false - Because we’re writing to InfluxDB, we don’t need to persist messages to disk.
log_dest stdout - For setting up, testing, and debugging, outputting logs directly to the terminal makes things easier.

And of course, make sure your listener is configured on the same port for all devices. The default is 1883, but you can change this if desired.

Once you configure your broker, you can set up your publishing clients, and with whatever data you’re measuring, they can publish messages to the broker with the command:

mosquitto_pub -h "host" -t "topic" -m "value"

If you’re running this all on a local network, your host will be localhost; otherwise, it’ll be the address where your broker is running. The value should be whatever you’re measuring and publishing at that moment.

Your topic can be whatever is appropriate to label that value. If you have different devices and different types of measurements for each device, it’s recommended to nest your topics and organize them in a way that makes logical sense. For example, if you have many different devices measuring, say, temperature and velocity, your topic arrangement may look like:

/sensors/vehicles/v1/device1/temp
/sensors/vehicles/v1/device1/velocity
/sensors/vehicles/v1/device2/temp
/sensors/vehicles/v1/device2/velocity

As long as you have a unique topic structure for each type of value being sent, we can parse and sort this into tags and fields with InfluxDB. For further information on setting up MQTT topics, there are plenty of great guides on the matter.

With your clients and broker configured, your clients publishing messages, and your broker receiving and forwarding those messages, you should be all set up for the MQTT portion of this data pipeline.

Installing InfluxDB

The next step is to move your MQTT data into InfluxDB. The first step is to install InfluxDB. You can check out our docs on installing it here, but the simplest and easiest way to get started is to run the install scripts provided by InfluxData with:

curl -O https://www.influxdata.com/d/install_influxdb3.sh \
&& sh install_influxdb3.sh

These should work on every operating system and provide you with some simple options to get started with InfluxDB 3 Core or Enterprise. The installation script should also give you an admin token, which you’ll want to store somewhere safe so you can use it for authentication. If you’d like to further configure your InfluxDB 3 instance, the installation script should tell you where all files and configuration files were installed for further adjusting, though it should run fine out of the box.

If you have Docker installed, you can also install the InfluxDB Explorer UI as part of this process, giving you an easy way to view, manage, and query your InfluxDB 3 instance. You can reach it by navigating to localhost:8888 in your browser, entering host.docker.internal:8181 for the server address, and providing the admin token.

Installing and Configuring Telegraf

With InfluxDB 3 installed and running, the last step to get the data pipeline operational is to install and configure Telegraf to connect our MQTT broker to InfluxDB. Telegraf installation varies by operating system and Linux distribution, so check out the Telegraf documentation on installation to find the right files or command to run.

If you’re on Mac or Linux, this will generate a default configuration file for you:

On Mac, install via Homebrew: /usr/local/etc/telegraf.conf
On Linux: /etc/telegraf/telegraf.conf

Otherwise, you’ll need to create an empty configuration file or generate one with telegraf config > telegraf.conf. Once you have located or created your configuration file, all that’s left to do is connect Telegraf to your MQTT Broker and InfluxDB.

InfluxDB is very easy to configure a connection to, and you can add these lines to the config file:

[[outputs.influxdb_v2]]
  urls = ["InfluxDB address & port"]
  token = "admin token"
  organization = "org name"
  bucket = "destination database"

The InfluxDB address and port should be wherever you have InfluxDB installed. If you’re running on a local network, this will be http://127.0.0.1:8181; otherwise, it’ll be the IP and port.
Token is the admin token you copied from installation.
Organization can be whatever you’d like to name it.
Bucket should be the name of the database you’re writing all your MQTT data to. You don’t have to create the database first.

Setting up a connection to your MQTT broker is also straightforward:

[[inputs.mqtt_consumer]]
  servers = ["broker address"]
  topics = ["list of topics"]
  data_format = "value"
  data_type = "data_type"

  ## if you have username and password authentication for MQTT
  username = "username"
  password = "password"

The broker address is one again the address and port for where your MQTT broker is running. For a local network, this will be tcp://127.0.0.1:1883
Topics is a comma-separated list of topics that you’re writing to.
Data type is the primitive data type being written: integer, float, long, string, or boolean.

This is all you need in your configuration file to have the full pipeline running! If you run telegraf with telegraf --config telegraf.conf, you should be able to send a message from an MQTT publisher and view that data in InfluxDB.

However, you can make some improvements in Telegraf’s configuration to help parse and organize your data by topic. By default, this writes each topic into a single tag column to the same table, with a monolithic “value” column for all your values, which isn’t a very good data model. With topic parsing and pivot processing added to the configuration, we can specify what part of the topic should define what table the data is written into, turn every level of the topic into a tag, and pivot on the last level of the topic so that each raw value is its own field:

[[inputs.mqtt_consumer]]
  servers = ["broker address"]
  topics = ["/sensors/#"]
  data_format = "value"
  data_type = "data_type"

  ## if you have username and password authentication for MQTT
  username = "username"
  password = "password"

  [[inputs.mqtt_consumer.topic_parsing]]
    measurement = "/measurement/_/_/_/_"
    tags = "/_/device_type/version/device_name/field"
  [[processors.pivot]]
    tag_key = "field"
    value_key = "value"

This takes a value from the /sensors/vehicles/v1/device1/temp topic and writes it to the sensors table. The tag columns populate with device_type = vehicles, version = v1, device_name = device1, and temp is written as a field with the value of temp set to whatever your MQTT publisher wrote. You can modify this configuration as appropriate for your topics, and the documentation provides full information on everything that can be done.

Further improvements

With MQTT data being published, parsed, and written into InfluxDB, you’ve fully set up an MQTT data pipeline! However, there’s a lot more you can do:

View and query your data with the InfluxDB Explorer UI, as discussed earlier.
Connect any one of the many client libraries to access your data and use it for downstream applications, or to a data visualization tool for dashboarding and insight into what’s being written.
Use the InfluxDB 3 processing engine for further transformations and processing of your data as it’s written.
Set up alerts, monitoring, forecasting, and more with the processing engine, too.

The final product

By integrating MQTT, Telegraf, and InfluxDB, you’ve constructed a robust, fully-functioning data pipeline capable of efficiently centralizing real-time telemetry. The lightweight MQTT protocol ensures that messages from your distributed network flow reliably to the broker, while Telegraf acts as the collection agent for seamless ingestion and transformation. Finally, InfluxDB provides the purpose-built storage and specialized features needed to query and visualize your data in minimal time. This architecture establishes a solid foundation for turning raw event streams into meaningful insights, minimizing your time to awesome.

From Edge to Cloud: How Litmus Edge and InfluxDB Unlock Industrial Intelligence at Hannover Messe

Ben Corbett (InfluxData) — Thu, 16 Apr 2026 06:00:00 +0000

If you’ve spent time in industrial environments, you know the problem isn’t a lack of data. It’s collecting it reliably, contextualizing it, and storing it at scale. Most stacks weren’t built to fight all three battles.

The industrial data problem

Industrial connectivity is no joke. OT environments are notoriously fragmented and siloed, spanning PLCs, CNCs, SCADA systems, and sensors, each speaking a different protocol, running on a different vendor’s stack, and operating in a network zone that was never designed to talk to anything outside the shop floor. Extracting value from that data has traditionally required heavy IT involvement, expensive integrations, and months of professional services work, and the traditional answer was usually a historian. Historians made progress on the access problem, giving individual sites a way to capture and store machine data. But standardizing that data across silos and contextualizing it across systems and plants is where they fall short. And unfortunately, that’s where most of the value lies.

Once data is collected and contextualized, the next problem is keeping it useful at scale. This is more than a storage problem. Sustaining high-frequency ingest of contextualized telemetry and querying that data fast enough to act on it is where most systems break. Historians were not designed for this. They sacrifice resolution, degrade under query load, and make cross-site, cross-system analysis slow and impractical. The value in industrial data is in the detail, and most platforms are architected to throw this detail away.

Collect, contextualize, and store—all at the edge

Litmus Edge acts as the intelligence layer between your machines and the rest of your data architecture. It connects natively to hundreds of industrial protocols, including OPC-UA, Modbus, MQTT, FANUC, Siemens S7, and many more, normalizing disparate machine data into a unified, consistent stream.

But connectivity alone isn’t enough. Raw machine signals mean little without context. Litmus Edge allows operations teams to tag, enrich, and structure data at the point of collection. A temperature reading becomes tied to a specific asset, production line, facility, and product run. By the time data leaves the edge, it is no longer just a number. It is a meaningful, queryable event.

Scale, query, retain: your industrial data hub

InfluxDB 3 becomes the system of record for your industrial time series data at the edge, in a centralized environment, or both.

It ingests high-frequency telemetry at full resolution, serves low-latency queries for real-time operations, and scales to fleet-wide analysis across sites and time horizons without forcing tradeoffs between fidelity and cost. High cardinality isn’t a problem to design around. Long-term retention doesn’t require a cost penalty. The data stays detailed, queryable, and useful.

Scaling across lines, sites, and the enterprise

Scale changes what’s possible, but only if the data model scales with it. When every site collects and contextualizes data the same way, writing to a consistent schema, cross-site analysis becomes straightforward. Comparing performance across plants, identifying outliers, and correlating signals across a global fleet become simple queries instead of integration projects. That consistency is what the Litmus and InfluxDB architecture is designed to deliver.

Which production lines across all facilities are showing early indicators of equipment degradation?
How does energy consumption per unit compare across sites running similar processes?
Where are the outliers? And what can the top performers teach the rest of the network?

These are not hypothetical future capabilities. They are available today to any organization willing to invest in getting the data foundation right.

The bridge to higher-level analytics

InfluxDB doesn’t just store data well; it integrates cleanly with the ecosystem: the analytics, visualization, and AI/ML tooling your teams are already investing in. Grafana dashboards, anomaly detection workflows, and digital twin platforms connect through InfluxDB’s SQL-native interface and open APIs without custom pipelines or bespoke integration work.

For OT teams, that’s the point. The edge handles the hard part—protocol translation, normalization, enrichment. InfluxDB centralizes the results into a single, interoperable data layer that every team can query with the tools they already use.

The result is a data architecture that is genuinely interoperable; the plant floor and the enterprise layer are finally speaking the same language.

Extending into the cloud with AWS

There are several ways to deploy InfluxDB as your industrial data hub: on-premises, at the edge, or in the cloud. For teams who want to go straight to the cloud, AWS is a natural fit. In this reference architecture, Litmus Edge writes contextualized telemetry directly into Amazon Timestream for InfluxDB, creating a seamless path from the shop floor to cloud-scale analytics. This allows teams to centralize access, scale analytics, and integrate with the broader AWS ecosystem without rebuilding their infrastructure from scratch.

Once data is available in AWS, it opens up a broader set of capabilities. For example, as new data arrives, you can trigger serverless workflows with AWS Lambda, stream high-velocity data through Kinesis for downstream processing, or connect directly to SageMaker to train models on high-fidelity data, without reshaping or downsampling it first.

What we’re showing at Hannover Messe

At Hannover Messe, you’ll be able to see this architecture running end-to-end:

Litmus booth (Hall 16, Stand A09): The full Digital Factory demo, showing how data flows from industrial systems into Litmus and into InfluxDB 3 Enterprise in real-time.
InfluxData kiosk (within the Litmus booth): A deeper look at how InfluxDB handles high-frequency ingest, real-time querying, and efficient storage at massive scale.
AWS booth (Litmus kiosk): The cloud extension of the demo, highlighting replication into Amazon Timestream for InfluxDB and integration with AWS services.

The InfluxData team (including myself) will be on-site at the Litmus booth throughout the event to walk through the architecture and discuss real-world deployment patterns.

Post by Ben Corbett, InfluxData; Rajesh Gomatam, Ph.D. Principal Partner Solutions Architect - Manufacturing, AWS; and Benjamin Norman, Partner Solution Architect, Litmus

What’s New in InfluxDB 3 Explorer 1.7: Table Management, Data Import, Transforms, and More

Daniel Campbell (InfluxData) — Wed, 15 Apr 2026 05:30:00 +0000

InfluxDB 3 Explorer 1.7 is a step forward for anyone who wants to manage their time series data without constantly switching between the UI and a terminal. This release adds table-level schema management, the ability to import data from other InfluxDB instances, and a new Transform Data section to reshape your data, all within the Explorer UI.

Table management

Previously, if you wanted to see what tables existed inside a database, you had to query system tables or use the API. The new Manage Tables page changes that. You can get there from the sidebar or from the new actions menu on any database in the Manage Databases page. That actions menu gives you quick access to query a database, view its tables, or delete it.

The Manage Tables page lists every table in the selected database, along with its column count, type, and any configured Distinct Value or Last Value Caches. Use the toggle filters to show or hide system tables and deleted tables. Deleted tables show up with a “Pending Delete” badge when the Show Deleted Tables toggle is enabled, so you always have visibility into what’s been removed.

You can also create new tables directly from this page. The Create Table dialog lets you define the schema up front: name, fields with data types, optional tags, and a retention period. This is useful when you want to control your schema explicitly rather than relying on schema-on-write to infer types from the first arriving data points.

From any table’s action menu, you can jump straight to the Data Explorer with a pre-built query for that table.

Import from InfluxDB

The next few features I’ll discuss are enhancements that make it much easier to work with the InfluxDB 3 Processing Engine.

Moving data between InfluxDB instances used to mean writing scripts, dealing with export formats, and coordinating tokens across environments. The new Import from InfluxDB feature provides a guided workflow for migrating small-to-medium datasets from any existing InfluxDB v1, v2, or v3 instance (assuming v3 Schema compatibility) into your current InfluxDB 3 database.

You’ll find it under the Write Data section, on both the Dev Data and Production Data pages. The workflow walks you through selecting a target database (or creating a new one), connecting to a source InfluxDB instance, authenticating, and then choosing which databases and tables to import.

Before committing to the import, perform a dry run that shows you exactly what will be transferred, including the source and destination, the number of tables, the estimated row count, and how long it should take. Advanced options let you tune the batch size and concurrency if you need to balance import speed against resource usage.

Once you start the import, a live progress view shows you how far along things are, how many rows have been imported, and the current status of each table. When it finishes, a “Query this database” button takes you straight to the Data Explorer so you can verify everything landed correctly.

If you’re running an InfluxDB 1.x or 2.x instance and want to try InfluxDB 3 with your real data, this saves you from building a migration pipeline. Just point the import tool at your existing instance, pick the databases and time range you want, and the data flows over. It also works for consolidating data from multiple InfluxDB 3 instances into one place, or pulling production data into a dev environment for testing.

Transform data

The new Transform Data section in the sidebar gives you a visual interface for setting up data transformations that run automatically on ingestion via the Processing Engine. Under the hood, these are powered by the Basic Transformation Processing Engine plugin, but you don’t need to write any plugin configuration by hand. The UI handles that for you.

The way it works: when data is written to a source table, the transformation runs automatically and writes the results to a target database or table. You can set a short retention period on the source data (say, one day) so the raw data cleans itself up, and the transformed data lives on in the destination. There are four types of transformations available.

Rename Table

Rename Table lets you route data arriving in one table to another table. This is handy when you’re consuming data from a source you don’t control, and the table names don’t match your naming conventions.

Rename Columns

Rename Columns works similarly, but at the column level. You pick a source table and select which columns to rename. If you’re integrating data from different systems that use different naming conventions (for example, temp_f vs temperature_fahrenheit), this standardizes everything without touching the source.

Transform Values

Transform Values lets you apply calculations or conversions to field values as they come in. You can do math operations, string transformations, unit conversions, or simple find-and-replace. If your sensors report temperature in Celsius but your dashboards expect Fahrenheit, this handles the conversion at ingestion time so your queries stay clean.

Filter Data

Filter Data lets you keep only the rows or columns that match specific conditions. You can filter by rows (e.g., only keep data where crop_type = 'carrots') or by columns (drop fields you don’t need). This is useful when you’re receiving more data than you actually want to store. For example, a third-party feed might send 50 fields when you only care about 5.

You can test each transformation before deployment, and once deployed, monitor its status (running, stopped, errors) from the Transform Data dashboard.

Downsample Data

Downsampling is a classic time series operation: take high-frequency data and roll it up into lower-frequency summaries to save storage and speed up queries over long time ranges. The new Downsample page, also under the Transform Data section, makes this easy to set up. You create a downsample trigger by specifying a source table, a target table, a schedule (how often the aggregation runs), a time window (how far back to look), an aggregation interval (the bucket size), and an aggregation function (avg, sum, min, max, etc.). You can also choose to include or exclude specific fields.

The Downsample Processing Engine plugin powers this feature.

Get started

All of these features are available now in InfluxDB 3 Explorer 1.7. For more on these Processing Engine capabilities, see InfluxDB 3 Processing Engine Updates.

If you’re running InfluxDB 3 Core or Enterprise, update to the latest version to try them out. To learn more, check out the InfluxDB 3 Explorer documentation.

To update InfluxDB 3 Explorer, pull the latest Docker image: docker pull influxdata/influxdb3-ui

Less Friction, More Control: Here's What Shipped in Q1

Ryan Nelson (InfluxData) — Wed, 08 Apr 2026 08:00:00 +0000

Our Q1 momentum has been focused on a simple goal: making InfluxDB easier to operate, easier to scale, and faster to put to work.

Across Telegraf, InfluxDB 3, and our managed offerings, these updates reduce friction in how teams collect, process, and scale time series workloads.

Telegraf Controller enters beta

Telegraf is already a powerful way to collect metrics, logs, and events across environments. At scale, the challenge shifts from collection to control. Telegraf Enterprise is designed to solve that problem.

At the center is Telegraf Controller, a control plane that gives teams centralized configuration management and fleet-wide health visibility. The beta includes major capabilities such as API authentication, API token management, user account management, multi-user support, role-based access control, global settings management, and expanded plugin support in the visual config builder.

Feedback from early users is shaping the road to general availability, with enterprise licensing, enforcement, audit logging, and federated identity management next on the roadmap. Sign up to join the beta.

InfluxDB 3.9 adds more operational control

Last week’s release of InfluxDB 3.9 is focused on making the platform easier to run at scale, with improvements aimed at predictability, visibility, and day-to-day management. The release expands CLI and automation support for headless environments, improves resource and lifecycle management, and adds clearer visibility into access control and product identity across Core and Enterprise deployments. These are the changes that matter in production: fewer rough edges, stronger operational clarity, and better control as workloads grow.

InfluxDB 3.9 Enterprise also includes a new beta performance preview for non-production environments. This optional preview includes optimized single-series queries, reduced CPU and memory spikes under load, support for wider and sparser schemas, and early automatic distinct value caches to reduce metadata query latency. These features are not yet recommended for production, but they give customers an early look at capabilities planned for future releases and a chance to help shape what comes next.

Processing Engine updates make InfluxDB 3 easier to operationalize

The Processing Engine remains one of the most powerful parts of InfluxDB 3 because it allows teams to run logic directly at the database. Users can transform data on ingest, run scheduled jobs, or serve HTTP requests without adding external services or layering on more pipeline complexity.

This quarter, we continued to expand both the engine itself and the plugin ecosystem around it. The latest plugins make it easier to get data into InfluxDB 3 from more sources:

The Import Plugin provides a simpler path for bringing data from InfluxDB v1, v2, or v3 into InfluxDB 3 Core and Enterprise, with support for dry runs, progress tracking, pause and resume, conflict handling, and flexible filtering.
New MQTT, Kafka, and AMQP subscription plugins help users ingest streaming data directly from external message brokers.
The new OPC UA Plugin gives industrial teams a more direct path to data from PLCs, SCADA systems, and other OPC UA-enabled equipment.

We also made important improvements to the Processing Engine itself:

New synchronous write controls give plugin authors more flexibility over durability and throughput.
Batch write support improves efficiency for high-volume workloads.
Asynchronous request handling keeps status checks and control operations responsive during long-running jobs.

Together, these updates make the Processing Engine a more practical way to build and operate real-time data pipelines directly inside InfluxDB 3. Check out our docs to learn more.

Better visibility for Cloud Dedicated customers

As teams run production workloads on Cloud Dedicated, understanding how the system is being used becomes just as important as performance itself.

This quarter, we introduced:

Query History (GA) for troubleshooting, performance analysis, and deeper insight into query activity.
S3 API dashboards (Tier 1 and Tier 2), including monthly usage visibility.

These updates give teams better visibility into system behavior, usage patterns, and a faster path to understanding activity across the environment. Detailed docs here.

InfluxDB Enterprise 1.12.3 delivers efficiency gains for v1 environments

For teams needing more performance and running large-scale v1 Enterprise environments, InfluxDB Enterprise 1.12.3 is now available with substantial improvements in efficiency and reliability:

100x faster retention enforcement for high-cardinality datasets
30% lower CPU usage during compaction
5x faster backups with configurable compression
3x less disk I/O during cold shard compactions

These improvements make Enterprise v1 clusters more efficient, more predictable under load, and more cost-effective to operate. Read the release notes.

Amazon Timestream for InfluxDB adds a new scale tier and simple upgrade path

InfluxDB 3 on Amazon Timestream for InfluxDB now supports clusters of up to 15 nodes, giving customers a new scale tier for more demanding real-time workloads.

This expanded tier improves query concurrency, increases ingestion throughput, and provides stronger workload isolation across ingestion, queries, and compaction. For teams running high-velocity, high-resolution data in production, that means more headroom to scale without compromising real-time performance.

Customers can also seamlessly migrate from InfluxDB 3 Core to InfluxDB 3 Enterprise, making it easier to move into this higher-performance tier without a manual architectural overhaul or data loss. The new 15-node option is available for InfluxDB 3 Enterprise in all AWS regions where Amazon Timestream for InfluxDB is offered. Read more here.

Looking ahead

Taken together, these updates are about helping teams do more with less friction: move data faster, operate with more confidence, and scale time series workloads without losing control. As operational data becomes more central to modern systems, we are continuing to invest in the infrastructure that turns that data into action across edge, cloud, and distributed environments.

New Plugins, Faster Writes, and Easier Configuration: What’s New with the InfluxDB 3 Processing Engine

Gary Fowler (InfluxData) — Tue, 07 Apr 2026 08:00:00 +0000

The Processing Engine is one of the most powerful features in InfluxDB 3. It lets you run Python code at the database—transforming data on ingest, running scheduled jobs, or serving HTTP requests—without spinning up external services or building middleware. You define the logic, attach it to a trigger, and the database handles the rest.

Since launching the Processing Engine, we’ve been building out both the engine itself and the ecosystem of plugins that run on it. Today, we want to walk you through some exciting recent additions: new plugins for data ingestion, import, and validation; some general improvements to the engine; and a better configuration experience using InfluxDB 3 Explorer.

A quick refresher: Processing Engine plugins

If you’re already familiar with the Processing Engine, feel free to skip ahead. For those newer to the concept, here’s the short version.

A plugin is a Python script that runs inside InfluxDB 3 in response to a trigger. There are three trigger types: data writes (react to incoming data as it’s written), scheduled events (run on a timer or cron expression), and HTTP requests (expose a custom API endpoint). Plugins have direct access to the database: they can query and write without having to egress and ingress the data to a different machine or location. Plugins can also talk to other systems, letting you utilize data from other places or systems.

You can write your own plugins from scratch to solve problems specific to your environment. That’s the whole point of embedding Python in the database: your logic, your rules, running right next to your data.

But we also know that not everyone wants to start from a blank page. That’s why we maintain an official plugin library with production-ready plugins for common time series tasks, such as downsampling, anomaly detection, forecasting, state change monitoring, and sending notifications to Slack, email, or SMS.

These official plugins are designed to work in two ways. You can install them and use them as-is, configuring them through trigger arguments or TOML files to fit your setup. Or you can treat them as templates: fork one, customize the logic, and build something tailored to your exact workflow. Either way, they’re meant to get you moving faster.

One more thing worth mentioning: if you’re thinking about building a custom plugin but aren’t sure where to start, AI tools like Claude can be very effective. Point Claude to the Processing Engine documentation and the plugin library repo for examples, describe what you want your plugin to do, and let it generate a first draft. We’ve seen simple plugins created in a single shot, from description to working code, and even more complex plugins come together quickly when the AI has good examples to work from. It’s a great way to get past the blank-page problem and into something you can iterate on.

New plugins: data ingestion, import, and validation

We’ve recently added several new plugins to the library that address some of the most common requests we’ve been hearing from the community. These are available now in beta—they’re fully functional, but we want to see them tested across more environments before we call them production-ready. Give them a try and let us know how they work for you.

InfluxDB Import Plugin

If you’re running an older version of InfluxDB and want to bring your data into InfluxDB 3, the new Import Plugin makes that significantly easier. It supports importing from InfluxDB v1, v2, or v3 instances over HTTP, with features you’d expect from a serious import tool: automatic data sampling for optimal batch sizing, pause/resume for long-running imports, progress tracking, tag/field conflict detection and resolution, configurable time ranges and table filtering, and a dry run mode so you can preview what an import will look like before committing to it.

The plugin runs as an HTTP trigger, so you control the entire import lifecycle (start, pause, resume, cancel, check status) through simple HTTP requests. That means you can kick off a large import, pause it during peak hours, and pick it up later from exactly where it left off. For small or medium-sized InfluxDB databases, some might even use this as a migration tool to move to InfluxDB 3.

Data subscription plugins: MQTT, Kafka, and AMQP

These three plugins let new InfluxDB 3 users start getting data into InfluxDB 3 fast and without coding. They let you subscribe to external message brokers and begin automatically ingesting that data into InfluxDB 3.

The MQTT Subscriber Plugin connects to an MQTT broker, subscribes to topics you specify, and transforms incoming messages into time series data. It supports JSON, Line Protocol, and custom text formats with regex parsing, and uses persistent sessions to ensure reliable message delivery between executions.

The Kafka Subscriber Plugin does the same for Kafka topics. It uses consumer groups for reliable delivery, supports configurable offset commit policies (commit on success for data integrity, or commit always for maximum throughput), and handles JSON, Line Protocol, and text formats.

The AMQP Subscriber Plugin rounds out the trio with support for RabbitMQ and other AMQP-compatible brokers. Like the others, it supports multiple message formats, flexible acknowledgment policies, and comprehensive error tracking.

OPC UA Plugin

For industrial environments, the new OPC UA Plugin connects directly to PLCs, SCADA systems, and other OPC UA-enabled equipment. It polls node values on a schedule and writes them into InfluxDB 3 with automatic data type detection. You can list specific nodes for precise control, or use browse mode to auto-discover devices and variables across large deployments. The plugin maintains a persistent connection between polling intervals and supports quality filtering, namespace URI resolution, and TLS security.

Now, you might be thinking: “I’m already using Telegraf to interface with my streaming data services or OPC UA, why do I need these?” If Telegraf is working well for you, that’s great; there’s no need to change what isn’t broken. But if you’re newer to InfluxDB and aren’t yet a Telegraf user, these plugins give you another way to quickly get data flowing into InfluxDB 3 without adding another component to your stack.

All three plugins share a consistent configuration model: you can set them up with CLI arguments for simple cases or TOML configuration files for more complex mapping scenarios. They all include built-in error tracking (logging parse failures to dedicated exception tables) and write statistics so you can monitor ingestion health over time.

Schema Validator Plugin

One of the benefits of InfluxDB is that you don’t have to pre-define a schema. Data gets written as it is received. But for some use cases our customers have, they do want to constrain incoming data to conform to a specific schema.

The Schema Validator Plugin addresses that challenge, ensuring only clean, well-structured data makes it into your production tables. You define a JSON schema that specifies allowed measurements, required and optional tags and fields, data types, and allowed values. The plugin sits on a WAL flush trigger and validates every incoming row against your schema. Rows that pass get written to your target database or table; rows that fail get rejected (and optionally logged so you can see what’s being filtered out).

A typical pattern is to write raw data into a single database or table, let the validator check it, and have clean data land in a separate database or table. It’s a straightforward way to build a reliable data pipeline without external tooling.

Processing Engine general improvements

Alongside the new plugins, we’ve made several improvements to the Processing Engine itself that give plugin authors more control over write behavior, throughput, and concurrency.

Synchronous writes with durability control. New synchronous write functions let you choose between two modes: wait for the write to persist to the WAL before returning (for cases where you need to query the data immediately after writing), or return immediately for maximum throughput. This means you can treat bulk telemetry data as a fast path while ensuring that coordination states, such as job checkpoints or configuration flags, are immediately durable and queryable.

Batch writes. If your plugin writes thousands of points, the overhead isn’t in the data itself; it’s in the repeated write calls. The new batch write capability lets you group many records into a single write operation, which can dramatically improve throughput and make memory usage more predictable.

Asynchronous request handling. Request-based triggers now support concurrent execution. Previously, request handlers processed one request at a time, which meant a slow request would block everything behind it. With asynchronous mode enabled, the engine can handle multiple requests concurrently, so status checks, control commands, and other lightweight requests stay responsive even while a heavy operation is running.

These improvements work together in practice. The Import Plugin, for example, uses batch writes with fast-path durability for bulk data transfer, synchronous durable writes for checkpoints and state, and async request handling to keep its pause/resume/status endpoints responsive during long-running imports.

Easier plugin configuration in Explorer

We’ve also been improving InfluxDB 3 Explorer to make configuring plugins simpler, especially for the plugins in the library.

Until now, configuring a plugin meant passing all the right parameters as startup arguments to the Python script or specifying them in a TOML file. That works, but it requires you to know exactly which parameters a plugin expects—which means reading the documentation first.

We’re adding dedicated UI configuration forms for some of the plugins in Explorer. Instead of assembling a string of key-value pairs, you’ll see a form with all the available options laid out, along with descriptions and example values. Required fields are clearly marked, and the form handles the formatting for you. It’s the same configuration under the hood, just a much more approachable way to get there.

This is especially helpful for plugins with more involved configuration, like the data subscription plugins. where you’re specifying broker connections, authentication, message format mappings, and field type definitions. The form-based approach removes the guesswork and lets you get a plugin running without bouncing back and forth between the docs and your terminal. So far, we have built a specific configuration for the Import, Basic Transformation, and Downsampling plugins.

This is what it looks like for the Import plugin:

This is what the Basic Transformation and Downsample configuration looks like:

Look for these to become available in Explorer in the next couple of months.

What’s next

We are continuing to improve the Processing Engine and the Plugin Library. We have an OPC UA plugin about ready for you to try, as well as some additional anomaly detection and forecasting plugins. And, we are building UI configuration for the data subscription plugins mentioned above to make them even easier to configure.

Try them out

All new plugins are now available in beta in the InfluxDB 3 Plugin Library. They require InfluxDB 3 v3.8.2 or later. Install them from the CLI using the gh: prefix, or browse and install them directly from InfluxDB 3 Explorer’s Plugin Library.

We’re releasing these as a beta because we want your feedback. We’ve tested them thoroughly internally, but real-world environments are always more diverse and more demanding than any test suite. If you run into issues, have ideas for improvements, or build something cool on top of these plugins, we’d love to hear from you: drop into the InfluxData Discord, post on the Community Forums, or open an issue on GitHub.

What’s New in InfluxDB 3.9: More Operational Control and a New Performance Preview

Peter Barnett (InfluxData) — Thu, 02 Apr 2026 12:00:00 +0000

We’ve spent the last few months listening to how teams are running InfluxDB 3 in the wild. The feedback was clear: as you scale, you need less “guesswork” and more control. Today’s release of InfluxDB 3.9 is our answer to that.

As more teams move InfluxDB 3 into production, our focus has shifted toward the operational experience: how you manage the database at scale, how you ensure it remains secure, and how you provide a seamless experience for users. This release is packed with a host of quality-of-life improvements and a beta of the key features we have planned for upcoming releases.

Whether you’re using the open source InfluxDB 3 Core for recent data and local workloads or scaling with InfluxDB 3 Enterprise for the full clustering and security suite, these 3.9 updates are designed to make your stack more predictable.

Operational maturity and system transparency

In 3.9, we’ve focused on making the database more predictable and transparent for operators. We have organized these refinements into three key areas:

Advanced CLI & Automation: We’ve expanded the CLI to better support complex, headless environments. This includes new flags for non-interactive automation and data validation, alongside support for unique host overrides to target specific node types in a cluster. We’ve also improved how Parquet query outputs are piped, making it easier to integrate InfluxDB into automated data pipelines.
System Reliability & Resource Management: We’ve refined how the database handles resources and large-scale schemas. To better support complex data, we’ve increased the default string field limit to 1MB. We’ve also hardened the database lifecycle; administrative controls are now more rigorous, and we’ve ensured that background resources, such as triggers, are cleanly decommissioned whenever a database is removed.
Visibility & Under-the-Hood Infrastructure: We’ve upgraded our core infrastructure to improve both security and operational clarity. This includes upgrading DataFusion and the bundled Python for more efficient query execution and plugin security. Additionally, the system now provides better visibility into access control and product identity, updating metrics, headers, and metadata access to clearly distinguish between Core and Enterprise builds across your stack.

Collectively, these refinements remove the subtle points of friction that can accumulate as a system scales in production. By hardening resource management and streamlining automation, we’re ensuring that InfluxDB 3 remains a predictable, “set-it-and-forget-it” core for your infrastructure.

Now in beta: A new performance preview

Behind the scenes, we’ve been working on performance updates to InfluxDB 3. These improvements support large-scale time series workloads without sacrificing predictability or operational simplicity. This work lays the foundation for what’s coming in 3.10 and 3.11, specifically focusing on smoothing behavior under load and expanding the range of schemas InfluxDB 3 can handle.

Because performance in time series is highly dependent on specific workloads and cardinality, we are introducing these updates as a beta in InfluxDB 3 Enterprise. The beta is intended for testing in staging or development environments only. It allows you to explore and provide feedback on:

Optimized single-series queries: Targeting reduced latency when fetching single-series data over long time windows.
Resource smoothing: Testing reduced CPU and memory spikes during heavy compaction or ingestion bursts.
Wide-and-sparse table support: For handling schemas ranging from extreme column counts to ultra-sparse data tables (or any combination).
Automatic distinct value caches: Early-stage, auto-creation of caches designed to reduce friction and eliminate metadata query latency.

These updates are available as an optional, flag-gated preview in InfluxDB 3.9 Enterprise. They are not recommended for production workloads. We encourage Enterprise users to test these capabilities against their specific use cases to help us refine the features for GA. InfluxDB 3 Core will also support many of these new features in the coming releases.

For instructions on how to enable these preview flags and to view the full technical requirements, visit our official Enterprise documentation.

Download InfluxDB 3.9: Available now via our downloads page or latest Docker images.
Join the beta: If you are an InfluxDB 3 Enterprise Trial user, reach out to me in our Discord or Community Slack to learn how to enable these beta features.

What is MRO? Maintenance, Repair, and Operations Explained

Charles Mahler (InfluxData) — Tue, 31 Mar 2026 08:00:00 +0000

MRO stands for maintenance, repair, and operations. It refers to the activities, supplies, and services that keep equipment, facilities, and infrastructure running safely and efficiently. Every industry that relies on physical assets depends on MRO, whether that means replacing a worn bearing on a production line, restocking safety gloves in a warehouse, or servicing an HVAC system in a hospital.

Despite being one of the largest categories of indirect spending in most organizations, MRO is chronically under-managed. This article explains what MRO covers, why it matters, how maintenance strategies differ, and how it plays out across industries.

What is MRO?

MRO is a broad category that encompasses the indirect materials, maintenance activities, and operational support required to keep a business functioning. MRO includes everything from spare parts and lubricants to safety equipment, cleaning supplies, and the labor required to inspect, fix, and service physical assets.

The scope of MRO varies by organization, but it always sits outside of direct production. A replacement motor for a conveyor belt is an MRO item. The raw steel that travels on that conveyor is not. This distinction matters for accounting, procurement strategy, and inventory management.

Common MRO Supplies and Activities

MRO is easier to understand through concrete examples:

Category	Description	Examples
MRO supplies	Parts, materials, and consumables used to maintain equipment and facilities.	Spare parts (bearings, seals, belts, filters, motors), lubricants and greases, fasteners, hand and power tools, electrical components (fuses, contactors, wiring), safety equipment (gloves, goggles, hard hats, respirators), cleaning and janitorial products, adhesives and tapes, and facility consumables (light bulbs, HVAC filters).
MRO activities	Hands-on maintenance and repair work performed on assets.	Routine inspections, lubrication, electrical testing, equipment alignment, welding repairs, painting and corrosion protection, calibration, and full equipment rebuilds.
MRO services	Outsourced or contracted maintenance support.	Third-party maintenance contracts, on-call repair technicians, specialized inspections (non-destructive testing), and outsourced maintenance for complex assets.

Why MRO matters

MRO spending often accounts for a significant share of an organization’s operating costs, yet it receives a fraction of the strategic attention that direct materials get. The numbers make a compelling case for changing that.

The market is massive. The global MRO market was valued at roughly $715 billion in 2025 and is projected to grow steadily through the next decade, driven by aging infrastructure, the rise of predictive maintenance, and increasing demand for operational efficiency.
Downtime is extraordinarily expensive. A 2024 Siemens report found that unplanned downtime costs the world’s 500 largest companies a combined $1.4 trillion per year, roughly 11% of their annual revenues. At a facility level, costs vary by industry, but the averages are sobering: approximately $260,000 per hour in general manufacturing, and over $2 million per hour in automotive production. Even smaller manufacturers typically lose over $100,000 per hour of unexpected downtime.
Equipment failure is the leading cause of downtime. The average manufacturer faces an estimated 800 hours of equipment downtime annually. Equipment failure accounts for roughly 42% of unplanned downtime incidents, and base components like bearings, seals, and motors are the most common culprits. These are precisely the kinds of failures that a well-run MRO program is designed to prevent.
Proactive maintenance pays for itself. Research from McKinsey and others consistently shows that organizations implementing predictive maintenance programs see 18–25% reductions in overall maintenance costs and 30–50% reductions in unplanned downtime. The U.S. Department of Energy has reported a potential ROI of up to 10x on predictive maintenance investments. Reactive repairs, by contrast, cost three to five times more than planned maintenance once you account for emergency labor, expedited parts shipping, and cascading production losses.
Safety and compliance depend on it. Regulatory bodies across industries mandate specific maintenance activities and intervals. Falling behind on MRO creates safety hazards for workers, compliance risk for the organization, and potential legal liability.

Maintenance strategies: preventive, predictive, planned, and condition-based

Organizations typically employ a mix of strategies, and the trend across industries is a steady shift from reactive to proactive, data-driven approaches.

Preventive Maintenance

Preventive maintenance is scheduled work performed at fixed intervals to reduce the likelihood of failure. Oil changes every 500 operating hours, filter replacements every quarter, and belt inspections every month are all preventive activities. The advantage is predictability: you know what work is coming and can plan parts and labor accordingly. The drawback is that you may be replacing components that still have significant useful life remaining, which wastes money and materials.

Planned Maintenance

Planned maintenance is a broader category that includes any maintenance activity scheduled in advance, whether it follows a calendar-based interval, a usage-based trigger, or a condition-based alert. The defining characteristic is that the work is anticipated and resourced before it begins, as opposed to reactive or emergency maintenance. Planned maintenance also encompasses scheduled shutdowns and turnarounds, where equipment is taken offline deliberately for extensive servicing.

Condition-Based Maintenance

Condition-based maintenance (CBM) uses real-time monitoring of equipment health indicators like vibration, temperature, oil quality, and electrical signatures to trigger maintenance only when those indicators show that maintenance is actually needed. Rather than replacing a bearing on a fixed schedule, CBM replaces it when vibration analysis shows degradation has reached a threshold. This approach eliminates much of the waste inherent in time-based schedules while still catching problems before failure.

Predictive Maintenance

Predictive maintenance takes condition-based monitoring a step further by applying machine learning, statistical models, and trend analysis to forecast when a component is likely to fail. Where CBM reacts to current conditions, predictive maintenance anticipates future conditions based on patterns in historical and real-time data. Sensors tracking vibration, temperature, pressure, and acoustic signatures feed data into analytics platforms that can predict failures days or weeks in advance.

The results are striking: organizations with mature predictive maintenance programs report 35–45% reductions in unplanned downtime and an average ROI of around 250% within the first 18 months.

The movement from reactive to predictive maintenance is one of the defining trends in MRO. As IIoT sensors become cheaper and more accessible, even smaller manufacturers can begin shifting toward condition-based and predictive approaches.

MRO in manufacturing

In the manufacturing industry, MRO encompasses all indirect materials and maintenance activities required to keep a production facility running. It is everything that supports the production process without becoming part of the finished product.

Manufacturing MRO spending is often highly fragmented. A single plant might purchase thousands of distinct SKUs, such as motor drives, conveyor belts, lubricants, rags, and safety boots, from dozens of suppliers. The proportion of organizations using more than 250 MRO suppliers has grown from 6% to 15% in recent years. This fragmentation makes it difficult to negotiate volume discounts, track usage, or identify waste.

Common MRO priorities in manufacturing include reducing unplanned downtime on production lines, maintaining critical spares inventory for high-impact equipment, shifting from reactive to preventive or predictive maintenance, standardizing parts and suppliers to simplify procurement, and ensuring compliance with OSHA and environmental regulations.

Manufacturers that invest in structured MRO programs typically see improvements in overall equipment effectiveness (OEE), lower maintenance costs per unit of output, and fewer safety incidents.

MRO in aviation

Aviation has one of the most rigorous and regulated MRO environments of any industry. Aircraft MRO is governed by strict regulatory frameworks like the FAA in the United States and EASA in Europe. Every maintenance activity must be performed by certified repair stations, documented in detail, and traceable.

The four main categories of aviation MRO are airframe maintenance, engine maintenance, component maintenance, and line maintenance.

Aviation MRO is also where data-driven maintenance has seen some of its most advanced applications. Airlines use predictive maintenance platforms that analyze sensor data from aircraft systems to forecast component failures before they occur, minimizing aircraft-on-ground events and improving safety.

MRO in energy and utilities

Energy and utilities represent one of the most asset-intensive sectors for MRO. Power plants, refineries, pipelines, water treatment facilities, and electrical grids all require continuous maintenance to remain operational and safe.

The consequences of downtime in energy are particularly severe. Utilities face additional complexity from regulatory oversight and public safety requirements; a failed transformer or water treatment system affects entire communities.

This sector has been an early adopter of IIoT and predictive maintenance technologies. Real-time monitoring of turbines, generators, transformers, and pipeline infrastructure allows operators to detect degradation early and schedule maintenance during planned outages rather than responding to emergencies.

MRO procurement, inventory, and software

Three operational areas determine how well an MRO program actually performs on a day-to-day basis.

Area	Description and Key Strategies
Procurement	The process of sourcing and purchasing indirect materials. High transaction volume but low individual dollar value. Improvement strategies include consolidating suppliers, using blanket purchase orders, and implementing e-procurement platforms.
Inventory	Balancing part availability against carrying costs. Effective management relies on criticality-based stocking, min/max levels, and regular cycle counts. MRO inventory supports production but is not part of the finished product.
Software	Tools to plan, track, and optimize maintenance. Includes CMMS for work orders, EAM for lifecycle planning, and e-procurement tools to streamline purchasing.

The process of sourcing and purchasing indirect materials. High transaction volume but low individual dollar value. Improvement strategies include consolidating suppliers, using blanket purchase orders, and implementing e-procurement platforms.

Inventory

Balancing part availability against carrying costs. Effective management relies on criticality-based stocking, min/max levels, and regular cycle counts. MRO inventory supports production but is not part of the finished product.

Software

Tools to plan, track, and optimize maintenance. Includes CMMS for work orders, EAM for lifecycle planning, and e-procurement tools to streamline purchasing.

Where time series databases fit in an MRO strategy

The shift toward predictive maintenance creates a data infrastructure challenge that traditional systems were never designed to handle. A modern manufacturing facility with thousands of IIoT sensors can generate billions of data points daily. This is time series data, and it requires specialized tools at scale.

Traditional relational databases and legacy data historians struggle with the volume, velocity, and query patterns of high-frequency sensor data. Time series databases are built for this workload. They are designed to ingest large volumes of timestamped data at high speed, compress it efficiently for long-term storage, and support the kinds of queries that maintenance and operations teams actually need: trend analysis over time windows, anomaly detection, and correlation across multiple sensor streams.

InfluxDB is one of the most widely adopted time series databases in industrial environments. It is built to handle the data patterns that MRO and predictive maintenance generate, and it fits into the maintenance technology stack in several important ways.

Real-time equipment monitoring: InfluxDB ingests data from PLCs, SCADA systems, and IIoT sensors via standard industrial protocols like MQTT, OPC UA, and Modbus through its Telegraf agent. This creates a live feed of equipment health data that maintenance teams can use to spot anomalies as they develop.
Historical context for predictive models: Effective predictive maintenance depends on having deep historical data to train machine learning models. InfluxDB stores years of sensor data in a compressed columnar format, making it practical and cost-effective to retain the historical depth that ML models need to identify failure patterns.
Bridging OT and IT systems: One of the persistent challenges in MRO is that operational technology and information technology often exist in separate silos. InfluxDB integrates with both sides of this divide, connecting industrial data sources at the edge with analytics tools, cloud platforms, and AI/ML pipelines on the IT side.
Edge-to-cloud flexibility: Not every facility has the same infrastructure. Some need on-premises data processing for latency or security reasons; others want cloud-based analytics. InfluxDB supports deployment at the edge, in private clouds, or in fully-managed cloud environments, allowing organizations to match their data architecture to their operational reality.

The practical impact is tangible. Seadrill has reported saving over $1.6 million in a single year by using InfluxDB as its time series database for equipment monitoring. Siemens Energy uses InfluxDB to monitor 23,000 battery modules across more than 70 sites, analyzing billions of sensor readings to prevent downtime and ensure quality.

For operations and maintenance teams evaluating their data infrastructure, the key question is whether their current systems can handle the data volumes that condition-based and predictive maintenance demand. If the answer is no, a time series database is the foundational layer that makes advanced maintenance strategies possible.

Common MRO challenges

Even well-intentioned MRO programs run into recurring problems.

Fragmented Spending

This is the most widespread issue. When every department or site purchases MRO supplies independently, organizations lose leverage with suppliers and have no visibility into total spend.

Reactive Maintenance Culture

This culture remains entrenched in many organizations. ABB’s Value of Reliability research found that two-thirds of companies experience unplanned downtime at least once per month, and a full third have not undertaken motor or drive modernization projects in the past two years, even though upgrading obsolete equipment can generate ROI in less than two years.

Poor Data Quality

Poor data quality undermines almost every MRO improvement effort. Incomplete asset records, mislabeled parts, and patchy work-order histories make it difficult to decide what to stock, when to maintain, and where to invest. This problem compounds as organizations try to implement predictive maintenance, which depends entirely on clean, structured, time-stamped data.

Excess and Obsolete Inventory

Excess and obsolete inventory tie up capital and warehouse space. Parts ordered for equipment that has since been retired, or spares stocked based on outdated failure rates, accumulate quietly until someone audits the stockroom.

How to improve an MRO strategy

There is no single playbook for MRO improvement, but a few principles apply broadly.

Start with visibility. Before you optimize anything, you need a clear picture of what you are spending, where your inventory sits, and how your assets are performing. Consolidating data from procurement, maintenance, and inventory systems is almost always the first step.
Classify assets by criticality. Not all equipment deserves the same level of attention. Focus preventive and predictive maintenance resources on the assets whose failure would cause the greatest impact on safety, production, or cost.
Consolidate suppliers and standardize parts. Reducing the number of MRO suppliers simplifies procurement, improves negotiating leverage, and makes it easier to manage inventory. Standardizing on common parts across similar equipment reduces the total number of SKUs you need to carry.
Shift from reactive to proactive maintenance. This is a long-term cultural change, not a one-time project. Start with the highest-criticality assets, prove the value with condition monitoring and predictive analytics, and then scale. Organizations that make this transition consistently report dramatic reductions in both downtime and total maintenance cost.
Invest in the right data infrastructure. Advanced maintenance strategies are only as good as the data infrastructure behind them. This means CMMS/EAM software for work order management, time series databases for high-frequency sensor data, and integration layers that connect these systems so that insights flow from the sensor to the decision-maker without friction.
Measure what matters. Track metrics that connect MRO performance to business outcomes: planned vs. unplanned maintenance ratio, spare parts availability, mean time between failures (MTBF), overall equipment effectiveness (OEE), and maintenance cost as a percentage of asset replacement value.

Wrapping up

MRO may not be the most glamorous line item in an operating budget, but it is one of the most consequential. The organizations that treat maintenance, repair, and operations as a strategic function consistently outperform those that don’t. As sensor technology gets cheaper, predictive analytics gets smarter, and the data infrastructure to support them becomes more accessible, the gap between reactive and proactive organizations will only widen. The best time to invest in your MRO strategy was five years ago. The second-best time is now.

MRO FAQs

What does MRO stand for?

MRO most commonly stands for maintenance, repair, and operations—the activities, supplies, and services that keep equipment and facilities running. In aviation and heavy industry, MRO can also stand for maintenance, repair, and overhaul, where "overhaul" refers to the complete teardown, inspection, and rebuild of a component or system to original specifications. Both meanings describe the same core concept: sustaining operational readiness of physical assets.

What is MRO in business?

In a business context, MRO refers to all indirect spending related to keeping operations running. This includes everything from preventive maintenance schedules and spare parts to safety equipment, cleaning supplies, and facility consumables. MRO sits outside of direct production costs but has a significant impact on uptime, safety, and total operating expense.

What is the difference between MRO inventory and production inventory?

Production inventory consists of raw materials and components that become part of the finished product. MRO inventory includes spare parts, tools, consumables, and supplies used to maintain equipment and facilities; items that support production but never appear in the final product. Both require management, but they serve different purposes and are often handled by different teams with different procurement strategies.

What is MRO in manufacturing?

In manufacturing, MRO covers the indirect materials (lubricants, filters, PPE, tools, electrical components) and maintenance activities (inspections, repairs, preventive maintenance) required to keep production equipment operational. It is one of the largest categories of indirect spending in most manufacturing organizations.

What is MRO in aviation?

In aviation, MRO stands for maintenance, repair, and overhaul. It is a heavily regulated segment that includes line maintenance, airframe and engine maintenance, component repair, and full overhauls of aircraft systems. Aviation MRO is essential for airworthiness certification and passenger safety, and it is governed by regulatory bodies like the FAA and EASA.

What are MRO supplies?

MRO supplies are the materials purchased to support maintenance and operational activities. Common examples include spare parts, fasteners, lubricants, hand tools, safety gear, cleaning products, electrical components, and facility consumables like light bulbs and HVAC filters. These items are consumed during the maintenance process rather than incorporated into a finished product.

Why is MRO important?

MRO directly affects equipment uptime, workplace safety, regulatory compliance, and operating costs. Unplanned downtime alone costs U.S. manufacturers an estimated $50 billion per year. Organizations that manage MRO effectively experience fewer breakdowns, lower total maintenance costs, longer asset lifespans, and better safety records. As maintenance strategies evolve from reactive to predictive, the strategic importance of MRO continues to grow.

What is the difference between preventive and predictive maintenance?

Preventive maintenance follows a fixed schedule. For example, replacing a filter every 90 days regardless of its condition. Predictive maintenance uses real-time data from sensors to forecast when maintenance is actually needed, based on the condition and performance trends of the equipment. Predictive approaches reduce both unnecessary maintenance and unexpected failures, but they require investment in sensors, data infrastructure, and analytics tools.

What is a CMMS and how does it relate to MRO?

A CMMS (computerized maintenance management system) is software used to schedule, track, and document maintenance activities. It is one of the core tools in an MRO program, helping teams manage work orders, track asset history, plan preventive maintenance schedules, and monitor spare parts inventory. More advanced platforms (often called EAM, or enterprise asset management systems) add lifecycle planning, capital project tracking, and integration with other enterprise systems.

Telegraf Enterprise Beta is Now Available: Centralized Control for Telegraf at Scale

Scott Anderson (InfluxData) — Thu, 26 Mar 2026 07:30:00 +0000

Telegraf is incredibly good at what it does: collecting metrics, logs, and events from just about anywhere and sending them wherever you need. But once Telegraf becomes part of your production telemetry pipeline, spread across environments, teams, regions, and edge locations, the hard part isn’t installing agents; it’s operating them.

Configs drift. “Temporary” overrides linger. Rolling out changes across hundreds (or thousands) of agents becomes a careful, manual process. And when something breaks, the first question is rarely about the data—it’s about the fleet:

which configuration is running where, and is every agent healthy?

That’s the problem Telegraf Enterprise is built to solve.

Today, we’re opening the Telegraf Enterprise beta to the broader Telegraf community so you can help us validate the product where it matters most: at scale.

What is Telegraf Enterprise?

Telegraf Enterprise is a commercial offering for organizations running Telegraf at scale and needing centralized management, governance, and support. It brings together two key components:

Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and fleet health visibility.
Telegraf Enterprise Support: Official support for Telegraf Controller and official Telegraf plugins, designed for teams that need dependable response times and expert guidance.

It’s built for real-world, large-scale agent deployments, where Telegraf isn’t a tool you occasionally touch, but a platform you rely on.

Meet Telegraf Controller: your Telegraf control plane

At the heart of Telegraf Enterprise is Telegraf Controller, which centralizes two things teams struggle with most at scale:

Configuration Management That Doesn’t Collapse Under Growth

Telegraf Controller helps you create and manage configurations to support consistency across environments while still allowing necessary variation. Core capabilities include:

Centralized configuration creation and editing
Templates and parameterization to reuse configs safely
Label-based organization (so fleets don’t devolve into a long list of “agent-123”)
Bulk operations for fleet-wide changes
Environment variable and parameter management
Plugin metadata visibility to simplify config authoring and maintenance

Fleet-Wide Health Visibility

Telegraf Controller gives you a single view into the overall status of your agent deployments, so you can understand:

Which agents are reporting as expected
Where health issues are clustering
What changed recently, and what might be correlated

In other words, you don’t just manage Telegraf. You operate it.

Designed to fit your telemetry stack

Telegraf Enterprise is designed to work with the way teams actually deploy Telegraf.

It does not require InfluxDB. You can use the Telegraf Controller regardless of where your telemetry data is going.
Configuration delivery follows a pull-based model, where agents fetch configuration over HTTP. This keeps change management predictable and compatible with locked-down environments.
It’s built to support hundreds to thousands of agents, with production-grade storage options and a modern UI + API architecture for automation.

Why we’re running this beta

This beta is open to any Telegraf user who wants to test-drive Telegraf Controller.

The focus of the beta is simple:

Test Telegraf Controller at scale: We want to validate how well Telegraf Controller holds up when you connect real fleets—hundreds or thousands of agents—with real operational behaviors.
Gather feedback from the community: We’re intentionally inviting community input early, while we’re still shaping the GA experience. What workflows are missing? What’s confusing? What would make this tool indispensable in your environment?

At this stage, your feedback directly influences what Telegraf Enterprise becomes.

Enterprise support that matches production expectations

Operating telemetry pipelines is a production responsibility, and when Telegraf is part of that pipeline, you need support that understands the stakes.

Telegraf Enterprise includes support designed for teams that need:

Clear expectations for response and escalation
Coverage for Telegraf Controller and official Telegraf plugins
Help diagnosing issues and reducing operational risk as fleets grow

This is especially valuable when Telegraf is deployed across multiple teams, environments, or customer sites, where operational consistency matters as much as collection capability.

Who is Telegraf Enterprise for?

Telegraf Enterprise is built for organizations that manage Telegraf fleets at a meaningful scale, including:

Platform engineering and SRE teams
DevOps organizations operating across multi-cloud / hybrid / edge
Managed service providers delivering telemetry as a service
Compliance-sensitive teams that need standardized configurations and governance

If you’re running a small number of agents and are comfortable managing configs manually, you may not need Telegraf Enterprise today. But if Telegraf is everywhere—and your team is responsible for keeping it reliable—centralized control quickly becomes less “nice to have” and more “how did we operate without this?”

Packaging: free and enterprise options

Telegraf Controller

A free tier is available for teams that want centralized configuration management and visibility with pre-defined limits.

Telegraf Enterprise

For teams operating Telegraf as critical infrastructure, Telegraf Enterprise includes the Telegraf Controller packaged with enterprise support.

The key difference: the Telegraf Enterprise is built for scale and operational reliability, with support and capabilities aligned to production fleet management.

Getting started with Telegraf Controller

Telegraf Enterprise is designed for teams operating Telegraf as a core part of production telemetry pipelines. If Telegraf is already how you collect metrics, logs, and events across your infrastructure, Telegraf Controller is the missing piece that helps you operate that collection layer like a platform—not a pile of configs.

To join the beta, click here to opt in. Please share your feedback in-app with the feedback button or our slack channel #telegraf-enterprise-beta.

Join the beta, push it hard, share your use case, and what makes your workflow easier!

Unifying Telemetry in Battery Energy Storage Systems

Allyson Boate (InfluxData) — Thu, 19 Mar 2026 08:00:00 +0000

Battery energy storage systems (BESS) play a critical role in modern energy infrastructure. Utilities rely on these systems to balance renewable generation, stabilize grid operations, and respond to changing electricity demand. As deployments scale in size and complexity, operators require continuous insight into battery health, system performance, and grid interaction. Operators rely on telemetry generated across several operational platforms. Battery management systems monitor cell behavior, power conversion systems, and regulate energy flow, while plant control platforms track facility status. Energy management software and environmental sensors provide additional context about facility conditions.

In many deployments, however, this information remains scattered across separate monitoring environments. Operators often move between multiple dashboards to understand activity across a single facility. Many BESS operators are now adopting unified telemetry platforms that consolidate operational signals and create a clearer operational view of system behavior.

The operational reality of modern BESS systems

A battery energy storage facility is not a single system but a collection of specialized subsystems that manage energy storage, power conversion, and grid interaction. Each subsystem monitors a different aspect of facility performance and generates operational signals that help operators understand how the system behaves.

Several platforms produce these signals. Battery Management Systems (BMS) track cell-level conditions such as voltage, temperature, and state of charge to protect battery health. Power Conversion Systems (PCS), typically implemented through inverters, regulate how electricity flows between the battery and the grid.

Plant-level monitoring runs through SCADA platforms, which provide alarms, system status, and operational controls. Energy Management Systems (EMS) determine when energy should be stored or dispatched based on grid signals and market conditions, while environmental sensors monitor external factors such as ambient temperature.

Together, these systems create a continuous operational record of facility performance, but the resulting information does not always exist in a shared environment.

The fragmented reality of BESS telemetry

In most battery energy storage deployments, operational data originates from multiple independent platforms, as described above. This fragmentation reflects the modular design and deployment of energy storage facilities. Battery systems, power conversion equipment, and plant control platforms are frequently delivered by different vendors, each with its own software, data models, and monitoring tools.

Because these platforms monitor individual components rather than the entire facility, data is rarely consolidated automatically. Operators often rely on multiple dashboards to understand activity across a single storage site. Correlating events between subsystems may require switching between tools and manually comparing timestamps or operational signals.

The result? Operators have access to large volumes of operational information but lack a unified view of the facility as a whole. When events occur across multiple subsystems, understanding how those signals relate to one another requires time and effort.

Operational cost of data silos

Even small issues can require significant labor to diagnose. The data silos created by ala carte technologies prevent engineers from seeing how signals across the storage system relate.For example, a thermal anomaly—an unexpected rise in battery temperature—may require operators to review battery readings, compare inverter load behavior, and examine environmental conditions. Without a unified view of these signals, determining the cause can take time.

These delays affect both system reliability and financial performance. If operators cannot quickly determine why system capacity dropped or alarms triggered, dispatch readiness may be affected during critical market windows. Over time, slower investigations and delayed anomaly detection can lead to reduced system availability, higher operational overhead, and missed revenue opportunities.

What unified telemetry actually means

Unified telemetry consolidates operational signals from across the storage system into a shared data environment. Instead of storing data separately within subsystem platforms, telemetry from across the facility enters a common dataset.

In this environment, operational signals are stored as time-series data, or measurements organized by timestamp, allowing signals from different subsystems to be synchronized and analyzed together.

This shared dataset allows engineers to correlate signals that were previously isolated. Battery temperature trends can be examined alongside inverter load behavior, dispatch signals, and environmental conditions to better understand system performance. Instead of switching between monitoring platforms, operators can observe how signals across subsystems evolve together within a unified operational timeline.

How unified telemetry works

In many deployments, telemetry aggregation begins at the edge of the facility. Edge collectors connect to operational systems such as the BMS, PCS, SCADA platform, EMS and environmental sensors using industrial protocols such as Modbus, OPC-UA, or CANbus. These collectors ingest operational signals and convert them into structured telemetry streams.

From there, the data flows through streaming pipelines into centralized platforms. These pipelines handle ingestion, buffering, and transport of high-frequency signals so information from across the facility can be processed as a continuous operational stream.

Time series databases store and index this telemetry by timestamp, allowing engineers to query system behavior over time. Organizing operational signals this way enables teams to correlate events across subsystems, analyze performance trends, and investigate anomalies.

Because signals from different systems exist in the same time-aligned dataset, engineers can examine battery performance, inverter activity, dispatch signals, and environmental conditions together. This enables faster incident investigation and supports advanced analysis such as anomaly detection and predictive maintenance.

Operational impact

Unified telemetry changes how energy storage facilities are operated and how organizations manage risk, reliability, and revenue. When signals from battery systems, power electronics, and plant controls are analyzed together, operators gain a comprehensive view of facility behavior rather than having to reconstruct events across multiple monitoring platforms.

This visibility allows teams to detect anomalies earlier and respond to operational issues before they escalate. Faster diagnosis reduces downtime and helps maintain system availability during critical dispatch windows. In energy markets, maintaining dispatch readiness helps protect revenue during high-value trading periods.

ju:niz Energy Deployment

ju:niz Energy operates large-scale battery storage systems that provide grid services and trading flexibility in energy markets. Their systems collect thousands of data points per second on battery health, temperature, climate conditions, and system performance.

To manage this telemetry, ju:niz built a centralized monitoring architecture using Telegraf, Modbus, MQTT, Grafana, Docker, AWS, and InfluxDB. Operational signals from battery systems stream into a centralized time series platform, giving engineers a unified view of system behavior and eliminating the need for legacy Python monitoring scripts.

This architecture enables the ju:niz team to analyze battery telemetry in real-time, improve alerting accuracy, and support predictive maintenance strategies across their storage infrastructure.To see how ju:niz implemented unified telemetry for its operations, read the full case study or watch the webinar.

The bottom line

Battery energy storage systems generate telemetry across multiple operational platforms, but when that data remains fragmented, operators struggle to understand how the system behaves as a whole. Unified telemetry solves this by bringing operational signals into a shared, time-aligned dataset. As BESS deployments scale, this capability will become foundational for operating energy storage systems reliably, efficiently, and profitably.

Ready to build a unified telemetry architecture? Get started with a free download of InfluxDB 3 Core OSS or a trial of InfluxDB 3 Enterprise.

A New Scale Tier for Time Series on Amazon Timestream for InfluxDB

Pat Walsh (InfluxData) — Mon, 16 Mar 2026 08:00:00 +0000

When we first announced the availability of InfluxDB 3 Core and Enterprise on Amazon Timestream for InfluxDB last year, we set a new standard for managed time series on AWS. We gave developers a simple way to harness high performance at scale while removing the burden of infrastructure management.

But as our customers have taught us, “at scale” is a moving target. Across Industrial IoT, physical AI, and real-time observability, data is growing in both volume and resolution. When you move from minute-by-minute polling to sub-millisecond, high-fidelity telemetry, the pressure on the underlying database compounds. To stay ahead of that curve, developers need a platform that scales as fast as their workloads.

Today, we’re delivering that by expanding InfluxDB 3 on Amazon Timestream for InfluxDB to support expanding clusters up to 15 nodes. We’re also introducing a seamless migration path from InfluxDB 3 Core to InfluxDB 3 Enterprise, allowing teams to unlock this massive performance tier without friction, risk of a manual architectural overhaul, or any data loss.

Scaling for the mission-critical

At InfluxData, we’re seeing time series expand from infrastructure monitoring to the foundation for autonomous systems. In high-stakes environments like power grid management or autonomous vehicle navigation, increased latency is a significant operational risk rather than just a performance metric.

Previously, AWS Timestream’s support of InfluxDB 3 was focused on smaller, highly efficient configurations. By expanding to 15 nodes, we are providing major upgrades across three important areas:

Query concurrency: More nodes mean more hands on deck to process complex, concurrent queries. Large teams can now run heavy analytical workloads without impacting real-time dashboards or critical alerts.
Massive throughput: With a larger cluster, you can ingest millions of data points per second across hundreds of millions of unique series, maintaining real-time query performance.
Workload isolation and optimization: These expanded clusters enable true functional isolation between ingestion, queries, and compaction. This allows granular performance tuning optimized for your most demanding workloads.

Architected for enterprise demand

This new 15-node option is available for InfluxDB 3 Enterprise and is designed for organizations that require high availability, enhanced security, and the power to maintain high ingestion and real-time query performance across high-resolution, high-velocity datasets. InfluxDB 3 Core will continue to operate in single-node deployments.

By leveraging AWS infrastructure, you can spin up these expanded clusters in minutes directly from the AWS Console. With our new seamless migration capabilities, you can transition your existing Core workloads to Enterprise clusters with a single click. This ensures that as your data grows (from a few local sensors to a global fleet of devices), your database never becomes the bottleneck, and your team never has to worry about the downtime typically associated with a migration. These larger clusters are available today in all AWS regions where Amazon Timestream for InfluxDB is available, ensuring you can deploy and optimize mission-critical time series infrastructure wherever your data lives.

The foundation for physical AI

Our partnership with AWS is about meeting developers where they build. By integrating with services like AWS Lambda, SageMaker, and Kinesis, we’ve simplified the path from high-volume streams into Physical AI. This is the frontier where intelligence moves from the digital realm into the physical world.

Time series is the heartbeat of this transition, fueling a two-part lifecycle:

Training: Using massive volumes of historical data to establish baselines and “normal” patterns.
Inference: Streaming real-time data against those models to trigger automated, deterministic actions.

What makes our partnership with AWS unique is that we support both sides of this loop. With up to 15 nodes at your disposal, InfluxDB 3 has the headroom to act as a distributed inference engine, running predictive maintenance and anomaly detection against your data. This eliminates the latency tax of moving massive datasets between layers, ensuring that whether you are managing a robotic fleet or a smart grid, your autonomous systems can perceive and react with real-time precision.

What’s next?

The future of time series is about speed, precision, and scale. With today’s announcement, we’re handing you the keys to all three. By removing the barriers between single-node efficiency and enterprise-grade performance, we’re making it easier than ever to evolve your architecture as fast as your data grows.

We’re excited to see what the community builds with this new level of power. If you’re ready to scale your real-time workloads, head over to the AWS Console and start building.

What is Industry 4.0? Everything You Need to Know in 2026

Company (InfluxData) — Fri, 13 Mar 2026 08:00:00 +0000

Industry 4.0 is the term used to describe the fourth industrial revolution, a name given to the integration of physical and digital systems, which includes the internet of things (IoT) and artificial intelligence that are transforming a huge number of industries.

At a high level, its goal is to create an efficient, automated process for creating products or services that can be adapted quickly and efficiently to changing customer needs.

Industry 4.0 also includes concepts such as cloud computing, big data analytics, and machine learning to enable smarter production processes.

By using sensors and automation technology, manufacturers can collect real-time data on their machines and operations, which can be analyzed to make more informed decisions about how best to manage resources, optimize production lines, and reduce costs.

Industry 4.0 is leading manufacturers away from the traditional linear, push-based approach to production toward a new data-driven, customer-centric model. This “smart” manufacturing can help businesses remain competitive and stay ahead of the curve in terms of production capabilities, while also contributing to a more sustainable future.

The path to Industry 4.0

Let’s take a look at how we arrived at Industry 4.0 by looking to the past. This additional context will help give you a better understanding of why Industry 4.0 is important and why so many people think it is valuable to adopt these technologies.

First Industrial Revolution

The First Industrial Revolution, which took place in the late 18th and early 19th centuries, was characterized by the mechanization of production, the use of steam power, and the development of the factory system.

This revolution led to significant changes in manufacturing, transportation, and communication, and had a major impact on society and the economy.

Second Industrial Revolution

The Second Industrial Revolution took place in the late 19th and early 20th centuries. It was characterized by mass production of goods, the use of electricity, and the development of the assembly line.

Third Industrial Revolution

The Third Industrial Revolution, also known as the Digital Revolution, took place in the late 20th and early 21st centuries and was characterized by the adoption of computers and automation in manufacturing and other industries.

Fourth Industrial Revolution

Industry 4.0, also known as the Fourth Industrial Revolution, is the current trend of automation and data exchange in manufacturing technologies, including developments in artificial intelligence, the internet of things (IoT), and cyber-physical systems.

It’s seen as the fourth major revolution in manufacturing, following the mechanization of production in the First Industrial Revolution, the mass production of the Second Industrial Revolution, and the introduction of computers and automation in the Third Industrial Revolution.

Industry 4.0 key concepts and principles

Interoperability

Interoperability is a fundamental concept in Industry 4.0, emphasizing seamless communication and data exchange among systems, devices, and software platforms within an industrial environment.

As Industry 4.0 relies heavily on integrating diverse technologies such as IoT, AI, and cloud computing, ensuring these components work effectively together is crucial to realizing the full potential of a connected, intelligent manufacturing ecosystem.

Interoperability enables businesses to break down silos, streamline processes, and make better-informed decisions, ultimately leading to increased efficiency, productivity, and competitiveness.

To achieve interoperability, manufacturers must adopt standardized communication protocols, open architectures, and flexible data formats to facilitate a smooth flow of information across the entire production chain.

Virtualization

Virtualization is the creation of virtual representations of physical assets, processes, and systems within the industrial environment.

By using advanced technologies such as digital twins, simulation software, and augmented reality, virtualization enables manufacturers to test, analyze, and optimize their operations without impacting the actual production process.

Virtualization not only allows more efficient planning and decision making but also helps businesses identify potential bottlenecks or issues before they occur, resulting in reduced downtime, lower costs, and enhanced product quality.

At the same time, it promotes remote monitoring and control of industrial processes, allowing experts to collaborate and troubleshoot issues from any location, which improves overall operational efficiency.

Cyber-Physical Systems

Cyber-physical systems (CPS) are a core part of Industry 4.0, representing the seamless integration of computational and physical components. These systems enable real-time communication and data exchange between machines, humans, and digital networks, resulting in smarter, more efficient, and autonomous industrial processes.

Decentralization

Decentralization involves the shift towards distributed decision-making and autonomous control within industrial systems.

In the context of manufacturing, decentralization empowers machines, devices, and production units to make decisions and perform tasks independently, without centralized supervision or control.

This approach increases the agility and resilience of manufacturing operations and enables businesses to scale more effectively, as new components or devices can be seamlessly integrated into the existing network.

Modularity

Modularity, the ability to adjust production lines, processes, and equipment with minimal effort and downtime, is a key concept in Industry 4.0.

It emphasizes the importance of designing flexible, scalable, and adaptable systems that can be easily reconfigured or upgraded to meet changing market demands and technological advancements.

By embracing modularity, manufacturers can rapidly adapt to fluctuations in product demand, introduce new products, or incorporate emerging technologies, ensuring their operations remain agile and competitive.

Modularity also enables greater customization, as production lines can be adjusted to accommodate unique customer requirements or preferences.

What technologies are driving Industry 4.0?

Internet of Things

IoT is an important part of Industry 4.0, enabling businesses to optimize processes and become more efficient. With this technology, companies can deploy intelligent machines to automate processes and workflows, leading to higher accuracy and productivity.

IoT technology also makes it possible for machines and databases to communicate, allowing businesses to access real-time data. This improved data collection has enabled insights about productivity and efficiency, streamlining many processes in Industry 4.0.

Cloud Computing

Cloud computing enables new ways for organizations to develop agile digital operations. By using cloud computing, companies can reduce the time needed to deploy or upgrade applications and further benefit from scalability.

With cloud computing, manufacturers now have access to analytics data they did not previously have, enabling them to make informed, real-time decisions.

Edge Computing

Edge computing is the process of collecting and analyzing data at the edge of a network, closer to where it is generated. It’s at the opposite end of the spectrum from cloud computing, but it’s just as important for Industry 4.0 workloads.

This makes it ideal for applications that require real-time analytics, such as autonomous robotic systems and self-driving cars.

Edge computing also helps reduce network traffic by minimizing the need to send large amounts of data back and forth between devices and centralized data centers.

5G Networking

5G networks allow for faster communication and data transfer speeds, a huge factor in making Industry 4.0 viable. This ultimately makes the technology more accessible to businesses of all sizes and enables them to deploy IoT solutions at scale.

5G can enable companies to increase operational efficiency by supporting real-time decision-making and remote monitoring capabilities.

AI and Machine Learning

AI and machine learning are another key piece of making Industry 4.0 possible. Using AI, companies are able to automate processes, improve decision-making, and better analyze data.

Many industries are already using AI to increase efficiency, accelerate innovation, and reduce costs. In manufacturing, for example, AI can be used to optimize production lines, predict maintenance needs, and schedule resources more efficiently.

Cybersecurity

Collecting and analyzing more data is great, but it also opens up numerous potential vulnerabilities for businesses. No company wants to be in the news for leaking internal or customer data, or for not being able to function because critical infrastructure has been hacked.

Industry 4.0 requires sophisticated cybersecurity solutions that protect data at rest and in transit, detect malicious activity before it becomes a problem, and alert users when something is amiss. This can be accomplished through various measures such as encryption, intrusion detection systems, two-factor authentication (2FA), and network segmentation.

In addition to implementing security solutions, organizations should also develop a comprehensive cybersecurity strategy that covers personnel training and processes for responding to emergency situations. This way, businesses can be more prepared for any potential attacks or data breaches.

Digital Twins

Digital twins enable engineers to create virtual models of systems and processes that can be used to measure performance, anticipate variation, and even detect defects or dangers before they become issues in the physical world.

As a result of this technology’s high accuracy, digital twin simulations can substantially reduce design costs, improve operational efficiency and sustainability, enhance product quality, and promote workplace safety.

Furthermore, companies are leveraging the combination of digital twins’ advanced analytics capabilities and connected devices to optimize factory operations through remote commissioning, proactive maintenance, and streamlined troubleshooting.

Real-Time Data Analytics

Real-time analytics is an essential part of Industry 4.0, enabling businesses to monitor, analyze, and respond to operational and process changes with unprecedented speed and accuracy.

By utilizing IoT devices, sensors, and advanced analytics models, manufacturers can collect and process data in real time, allowing them to make data-driven decisions and adjustments on the fly.

3D Printing and Additive Manufacturing

3D printing and additive manufacturing are quickly becoming essential tools for businesses to maximize efficiency, reduce costs, and create complicated designs with ease.

For example, factories can print replacement parts on-site without having to call a supplier and wait for them to arrive. This means faster repairs and less downtime overall.

Additive manufacturing also allows companies to manufacture complex designs that were previously impossible with traditional manufacturing methods.

Robotics

In the context of Industry 4.0, robotics goes beyond traditional automation, incorporating advanced capabilities such as AI, machine learning, and sensor integration to create intelligent, adaptive, and versatile machines capable of performing complex tasks with precision and consistency.

This also includes collaborative robots, or “cobots,” which are designed to work alongside human operators, enhancing their capabilities and ensuring a safer, more ergonomic work environment. By using robotics, manufacturers can automate repetitive tasks, reduce human error, and reduce labor costs, while also enabling greater flexibility and customization in production.

Benefits of Industry 4.0

1. Improved productivity

One of the primary benefits of Industry 4.0 is improved productivity. Key 4.0 technologies, such as data analytics and machine learning, can be used to identify inefficiencies and optimize production processes.

Similarly, robotics and 3D printing can automate tasks, reducing the need for human labor and increasing manufacturing output.

2. Increased efficiency

By enabling smarter use of resources and more efficient processes, Industry 4.0 contributes significantly to reducing energy consumption, waste generation, and greenhouse gas emissions.

When companies adopt Industry 4.0 technologies, they can actively contribute to global sustainability goals while simultaneously improving their bottom line.

Predictive maintenance is a prime example. This proactive approach allows companies to monitor equipment performance in real-time, identify potential issues before they escalate, and schedule maintenance activities based on actual equipment conditions rather than fixed intervals.

Predictive maintenance minimizes unexpected downtime and costly repairs, extends equipment lifespan, reduces the need for frequent replacements, and reduces associated environmental impact. As an added bonus, equipment that is properly maintained also tends to run more efficiently in terms of power consumption and greenhouse gas emissions.

3. Improved quality

By identifying errors in collected sensor data, Industry 4.0 can also help improve product quality. Additionally, 3D printing can create prototypes that can be tested for quality before mass production begins.

4. Reduced costs

The implementation of Industry 4.0 technologies helps minimize expenses because these technologies can help improve productivity and efficiency, leading to reduced labor costs and waste.

5. Increased flexibility

Industry 4.0 helps to increase flexibility within manufacturing operations. Technologies such as 3D printing and robotics can be used to create customized products quickly and with minimal human labor.

The use of data analytics also helps companies respond to changes in customer demand, scaling production up or down when needed.

6. Enhanced safety

Thanks to advances such as robotics and machine learning, dangerous tasks can now be automated. This reduces the risk of worker injury and helps create a safer working environment.

7. More resilient supply chains

Adopting many Industry 4.0 technologies can help businesses strengthen their supply chains. By leveraging data analytics, businesses can monitor the production process in real time and detect small issues before they escalate into larger problems.

Plus, 3D printing and additive manufacturing can also be used to quickly produce replacement parts or components for machinery with little to no downtime. This helps companies maintain operations without disruption due to supply chain problems.

8. Improved customer experience

Industry 4.0 can help businesses improve their customer experience by providing insights into customer behaviors and preferences. Through data analysis, companies can identify areas where they need to focus their efforts in order to provide the best possible service or product.

Data can also help during the manufacturing process to help identify potential defects early, so customers don’t receive a faulty product.

Industry 4.0 challenges and risks

1. Implementation costs

Implementing Industry 4.0 technologies and practices can be expensive, particularly for smaller businesses. If a business doesn’t have the necessary financial resources to invest in these technologies, it may not see a return on the investment.

2. Cybersecurity risks

The integration of advanced technologies and the reliance on connected systems increase the risk of cybersecurity threats. Without robust cybersecurity measures in place, a business may be vulnerable to attacks, which can have serious consequences.

3. Culture challenges

Some businesses may be hesitant to adopt new technologies and practices due to concerns about costs and disruptions to their existing operations. If a business isn’t willing to adapt to new technologies and processes, it may struggle to compete with competitors that are more forward-thinking.

This can also apply to employees who aren’t familiar with new technologies and may be resistant to change, making it important to ensure that employees at all levels of the company understand how and why changes are being made.

Common Industry 4.0 use cases

1. Smart manufacturing

Smart manufacturing and smart factories are common Industry 4.0 use cases where adopting new technologies can improve productivity, make products more reliable, and keep workers safer.

Beyond the direct benefits to the company, smart manufacturing can benefit the environment by reducing waste and making production more efficient.

2. Agriculture

The advantages of incorporating Industry 4.0 in agriculture are substantial.

Precision farming techniques, powered by IoT sensors and data analytics, facilitate the targeted application of fertilizers, pesticides, and irrigation, reducing waste and minimizing environmental impact.

Robotics and autonomous machinery can also perform repetitive tasks, such as planting, harvesting, and monitoring, improving efficiency and freeing up valuable human resources.

Advanced data analysis also enables predictive modeling and forecasting, helping farmers make informed decisions on crop selection, planting schedules, and resource allocation.

3. Healthcare

By using IoT devices to collect health data, patients are able to get more personalized and effective healthcare. This can include everything from detecting emergency situations, such as a heart attack, to enabling the detection and mitigation of diseases before they become severe.

Robotics is also increasingly used during surgery to reduce human error and improve outcomes.

4. Supply chain management

Adopting Industry 4.0 technologies can enhance supply chain management by enabling better visibility, efficiency, and resilience.

Connecting components such as suppliers, manufacturers, distributors, and retailers, enables smoother information exchange, ensuring that all stakeholders have access to accurate and up-to-date data.

Predictive analytics and machine learning can help forecast demand patterns, optimize inventory levels, and identify potential disruptions, allowing supply chain managers to address issues and minimize risks.

Industry 4.0 tools

In this section, we’ll examine some tools useful for a variety of tasks involved in adopting industry 4.0 technology.

1. Data storage

Storing Industry 4.0 data at scale requires scalable, efficient solutions that can handle the high volume of data generated by interconnected devices and systems. Here are a few different options for storing your data:

2. Time series databases

Time series databases (TSDBs) are specifically designed to store time-stamped data from sensors and IoT devices. They offer high write and query performance, making them ideal for handling the high-frequency data typical of Industry 4.0 use cases. An example of a TSDB is InfluxDB.

3. Data historians

Data historians are specialized databases for storing and retrieving historical process data from industrial systems. They are optimized for handling time series data and offer capabilities like data compression, aggregation, and real-time querying. An example of a data historian is OSI PI.

4. Columnar databases

Columnar databases store data in columns rather than rows, which is well-suited for analytics and processing large datasets and is often used as a data warehouse. Columnar databases offer high query performance and data compression, making them suitable for storing and analyzing the vast amounts of structured data generated by Industry 4.0 systems.

5. Communication protocols

Several communication protocols are well-suited for Industry 4.0 systems, providing efficient and reliable data transfer between interconnected devices, machines, and software platforms. Here are some good options for communication protocols in Industry 4.0:

6. MQTT

MQTT is a lightweight, publish-subscribe messaging protocol designed for low-bandwidth, high-latency, and unreliable networks. Its low overhead and minimal resource requirements make it ideal for IoT devices and Industry 4.0 applications.

MQTT is widely used to connect sensors, actuators, and other devices to cloud platforms, enabling efficient data exchange and remote monitoring.

7. OPC Unified Architecture (OPC UA)

OPC UA is a platform-independent, service-oriented architecture developed specifically for industrial automation and communication. It provides secure and reliable data exchange between devices, machines, and software applications, regardless of the underlying platform or programming language.

OPC UA supports a wide range of data types and features with built-in security mechanisms, making it a popular choice for Industry 4.0 systems.

8. Advanced Message Queuing Protocol (AMQP)

AMQP is an open standard, application-layer protocol for message-oriented middleware. It supports flexible messaging patterns and offers reliable, secure communication between devices and applications. AMQP is well-suited to scenarios that require complex routing and guaranteed message delivery, making it a good fit for many Industry 4.0 applications.

Data Collection and Integration

One of the big challenges for Industry 4.0 is collecting data from a variety of devices that may communicate over different protocols, then sending it to various tools for storage and analysis. Let’s take a look at some options that make collecting and integrating data easier:

1. Node-RED

Node-RED is an open-source, flow-based programming tool for wiring together devices, APIs, and online services. It provides a browser-based visual interface for designing and deploying data flows, making it easy to connect and integrate various data sources, such as IoT devices, industrial sensors, and web services.

With a large library of prebuilt nodes and support for custom nodes, Node-RED allows users to build complex data pipelines and perform data transformations with minimal coding effort.

2. Telegraf

Telegraf is an open source, plugin-driven server agent for collecting and reporting metrics from different data sources. Telegraf supports a wide range of input, output, and processing plugins, allowing it to gather and transmit data from various devices, systems, and APIs to different storage platforms.

Its flexibility and extensibility make it suitable for Industry 4.0 applications, where diverse data sources are common.

3. Apache NiFi

Apache NiFi is an open source, web-based data integration tool for designing, deploying, and managing data flows. It offers a visual interface for designing data pipelines and supports a wide range of data sources, processors, and sinks.

NiFi is particularly well-suited to use cases that require complex data routing, transformation, and enrichment. With built-in security features and support for data provenance, NiFi ensures data integrity and traceability in Industry 4.0 environments.

Industry 4.0 best practices

Moving towards Industry 4.0 is a major endeavor for existing businesses and involves all areas of a business to work properly. In this section, let’s explore some best practices that can help you avoid major pitfalls that could hurt your business.

1. Have a clear strategy and goals

Above all else, you need a clear understanding of how adopting these new technologies will help achieve your business goals. If you can’t actually find concrete ways that this will help your business, don’t blindly invest resources in them. Some potential things to identify:

Specific technologies that will be used
Which processes could be automated
Metrics to measure success
Cybersecurity focus

The integration of advanced technologies and the reliance on connected systems increase the risk of cybersecurity threats. Implement robust cybersecurity measures to protect against these threats from day one, so you don’t regret it later on.

2. Collaboration

Industry 4.0 technologies often involve integrating systems and processes across different organizations. It’s important to collaborate with suppliers and partners to ensure that these systems and processes are integrated effectively.

3. Track results and iterate

Establish metrics before starting so you can measure progress against expected results. Based on progress, you need to be willing and able to change your strategy if necessary.

FAQs

What are the origins of Industry 4.0?

Industry 4.0 as a concept dates back to 2006, when the German government laid out a plan to maintain its manufacturing dominance in a paper that looked into the future of manufacturing and how companies would be impacted and need to adapt to emerging technologies. The concept was further refined in 2010 when the German Cabinet laid out their High-Tech Strategy 2020 plan, which defined five priorities that would be used to direct billions of dollars in government investment.

How are digital transformation and Industry 4.0 related?

Digital transformation and Industry 4.0 are often used interchangeably, but it's crucial to understand their unique characteristics and how they relate to each other. While both concepts involve adopting advanced technologies to improve business operations, Industry 4.0 specifically focuses on the manufacturing sector, whereas digital transformation encompasses a broader range of industries and applications. Digital transformation is the process of integrating digital technologies across a business's customer service, marketing, supply chain management, and internal operations. The goal of digital transformation is to optimize processes, enhance efficiency, and create new business models that drive growth and competitiveness. This transformation is achieved through the implementation of technologies such as cloud computing, data analytics, artificial intelligence, and IoT. Industry 4.0, on the other hand, is a subset of digital transformation that targets the manufacturing industry. It is often referred to as the Fourth Industrial Revolution, representing a new era of intelligent, connected, and autonomous manufacturing systems. Industry 4.0 leverages technologies like IoT, advanced analytics, robotics, and additive manufacturing to optimize production processes, improve product quality, and increase overall efficiency. Despite their differences, digital transformation and Industry 4.0 are closely related, as both aim to drive innovation and create value through the adoption of advanced technologies. In fact, Industry 4.0 can be considered a specific application of digital transformation within the manufacturing sector. As companies embark on their digital transformation journeys, embracing Industry 4.0 principles can provide a solid foundation for growth and success in manufacturing.

What is IT/OT convergence?

Businesses have traditionally been siloed between information technology (IT) and operational technology (OT). But in recent years, these worlds have started to merge in a process commonly referred to as IT/OT convergence. Better collaboration between IT and OT can add tremendous value to any business by providing greater visibility across the organization, improved data analysis capabilities, fewer manual processes, and a faster response to customer needs. By leveraging both sets of technologies, businesses can gain unprecedented control over their operations. IT/OT convergence involves integrating hardware, software, and networks traditionally used in OT with those used in IT. This integration synchronizes the two disconnected systems, allowing them to exchange data and information. For example, an IT system can enable operators to access real-time operational data from OT systems, such as sensors and actuators.

What is Industry 5.0?

Industry 5.0 is a term used to describe the next phase of the Fourth Industrial Revolution, characterized by the integration of advanced technologies such as AI, IoT, and quantum computing into manufacturing and other industries. There isn't a universally accepted definition of Industry 5.0, and the concept is still evolving. However, it's generally seen as a continuation of the trend towards increased automation and data exchange that began with Industry 4.0, with a focus on even more advanced technologies and their integration across sectors. One key difference between Industry 4.0 and Industry 5.0 is the focus on sustainability and social responsibility. Industry 5.0 is expected to involve the development of technologies that are more environmentally friendly and that promote social equity. This could include using renewable energy sources and developing technologies to reduce waste and pollution. Overall, the main difference between Industry 4.0 and Industry 5.0 is the level of technological advancement. Industry 5.0 involves the integration of even more advanced technologies, such as quantum computing, which have the potential to significantly impact and transform various industries.

InfluxData Blog

A Runnable Reference Architecture for Industrial IoT on InfluxDB 3

What is the InfluxDB 3 IIoT reference architecture?

What’s in the stack

The features it’s actually showing you

1. The Processing Engine – Python plugins running inside the database

2. Last Value Cache – single-digit-millisecond current state

3. Distinct Value Cache – fast cardinality on high-cardinality tags

When to bring in OPC UA: the Processing Engine plugin

How to drop the IIoT architecture into your environment

Try it yourself

Resources

A Runnable Reference Architecture for Network Telemetry on InfluxDB 3

What is the network telemetry reference architecture?

What’s in the stack

The features it’s actually showing you

1. A real multi-node cluster, with role-separated nodes

2. The Processing Engine – Python plugins in a multi-node cluster

3. Last Value Cache (LVC) and Distinct Value Cache (DVC), doing real work

4. Per-table retention – the right policy in the right place

Three integration patterns, side by side

Where to wire in real network data

Try it yourself

A note for AI agents

Resources

Community Spotlight: A Native iOS App for Your InfluxDB Data

What is Influx Dashboard?

Step 1: Download the App

Step 2: Connect to Your InfluxDB Server

Step 3: Build Your Dashboard

Step 4: Query Your Data

Step 5: Explore Your Charts

Step 6: Manage Your Servers

Why this matters

Get started

Building Real-Time Telemetry Pipelines for IRIG 106 compliance

The need for real-time telemetry in aerospace

What is IRIG 106?

Compliance vs. agility

Building a real-time, compliant telemetry pipeline

From ingest to insight

1. Acquisition

2. Decoding

3. Streaming Ingestion

4. Processing and Downsampling

5. Query and Visualization

Typical Deployment

Real-time telemetry in action

Faster flight-test analysis and decision-making

A Runnable Reference Architecture for Battery Energy Storage Systems on InfluxDB 3

Why BESS is a special case for time series

What’s in the stack

The features it’s actually showing you

1. Last Value Cache – sub-millisecond pack heatmaps

2. Distinct Value Cache – fast inventory queries

3. The Processing Engine – Python plugins running inside the database

Where to wire in real BMS, PCS, and SCADA data

Try it yourself

A note for AI agents

Resources

What's New in InfluxDB 3 Explorer 1.8: Streaming Subscriptions, Smarter Sample Data, Line Protocol Validation, and Retention Controls

Data Subscriptions: stream from MQTT, Kafka, and AMQP

Sample data, three ways

Static Sample Data Presets

Custom Datasets (with a Dash of AI)

Live data plugins, for real-time sample data

Line protocol validation and schema preview

Database and table retention

Get it while it’s hot

Getting Started with Home Assistant Webhooks & Writing to InfluxDB

What is Home Assistant?

Setting Up a Home Assistant Webhook

Full-Stack Example: Energy Price Monitoring

Adding more intelligence to your smart home with InfluxDB

Continual improvement

How to Use Time Series Autoregression (With Examples)

Understanding time series autoregression

Types of autoregressive models and their applications

AR(1) First-Order Autoregression

AR(p) Higher-Order Models