# InfluxData

The place for technical guides, customer observability & IoT use cases, product info, and news on leading time series platform InfluxDB, Telegraf, SQL, & more.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## An Introduction to AI Agent Observability

DevFeed: [An Introduction to AI Agent Observability](<https://devfeed.tech/articles/an-introduction-to-ai-agent-observability-126527.md>)

Original publisher: [Read original article](<https://www.influxdata.com/blog/ai-agent-observability-introduction/>)

Author: Charles Mahler (InfluxData)

Published: 2026-11-10T06:00:00Z

Content type: article

Language: en

Sources: [InfluxData](<https://devfeed.tech/sources/influxdata.md>)

Topics: [agent observability](<https://devfeed.tech/topics/agent-observability.md>), [ai observability](<https://devfeed.tech/topics/ai-observability.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [LLM observability](<https://devfeed.tech/topics/llm-observability.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [Multi-step AI processes](<https://devfeed.tech/topics/multi-step-ai-processes.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>)

Tags: [actions](<https://devfeed.tech/tags/actions.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-observability](<https://devfeed.tech/tags/agent-observability.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agent-observability](<https://devfeed.tech/tags/ai-agent-observability.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [all](<https://devfeed.tech/tags/all.md>), [also](<https://devfeed.tech/tags/also.md>), [and-best-practices](<https://devfeed.tech/tags/and-best-practices.md>), [application](<https://devfeed.tech/tags/application.md>), [application-monitoring](<https://devfeed.tech/tags/application-monitoring.md>), [article](<https://devfeed.tech/tags/article.md>), [audit](<https://devfeed.tech/tags/audit.md>), [autonomy](<https://devfeed.tech/tags/autonomy.md>), [best](<https://devfeed.tech/tags/best.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [developer](<https://devfeed.tech/tags/developer.md>), [introduction](<https://devfeed.tech/tags/introduction.md>), [observability](<https://devfeed.tech/tags/observability.md>)

### AI overview

AI agent observability records the models, tools, decisions, timing, costs, and outcomes of each run so teams can debug failures, control spend, review safety, and compare changes. It combines events, metrics, and traces; useful measures include cost per successful outcome, latency, tool failures, and approval activity. The source recommends beginning with one agent and one question, collecting metadata while keeping prompt and response content off by default, then adding views, an alert, and an outcome signal. OpenTelemetry offers portability across frameworks and vendors, while framework-native tracing is often quicker to start; its GenAI conventions are still evolving. Telegraf and InfluxDB are presented as an operations layer alongside trace viewers and evaluation platforms. Challenges include variable run behavior, sensitive data, high event volume, inconsistent telemetry, and linking agent activity to outcomes. Basic logs and provider usage dashboards may suffice for low-volume apps making a single model call.

### Source excerpt

AI agents have moved from simple demos to being critical parts of daily work. An agent plans, calls tools, reads the results, and keeps going until it decides the task is done. That autonomy is useful, but it also makes it hard to know what an agent did and what it cost at scale. This article covers what AI agent observability is, how it differs from application monitoring, which metrics to track, and best practices for getting started. What is AI agent observability? AI agent observability is the ability to see, measure and explain what an AI agent did during a task: which models it called, which tools it used, what it decided, how long it took, what it cost, and whether it succeeded. It gives you the record you need to debug a failed run, set budgets, answer audit questions, and compare versions of an agent. Think of it as a flight recorder for every agent run. When a run goes wrong or costs more than expected, you can replay it step by step and see where it went off course. Agent observability uses three kinds of signals: Events record each thing that happened, such as "the agent called a model" or "the agent ran a tool, and it failed." Metrics are running totals and rates, such as tokens used per hour or tool failures per day. Traces show the timeline of a single task, with each step in order and how long it took. Why AI agent observability matters AI agents spend money and take actions on their own, and they rarely behave the same way twice. Without observability, cost overruns show up on the invoice and failures show up as user complaints. Risky actions may never show up at all. Give the same agent the same request twice, and it may call different tools and use several times as many tokens as are needed. Running agents without visibility creates five kinds of risk: cost, reliability, security, compliance, and quality. A loop that retries a failing step, or a quiet switch to a more expensive model, can burn through a budget rapidly. Tools can fail silently whil

## Root Cause Analysis for Data Centers

DevFeed: [Root Cause Analysis for Data Centers](<https://devfeed.tech/articles/root-cause-analysis-for-data-centers-116423.md>)

Original publisher: [Read original article](<https://www.influxdata.com/blog/root-cause-analysis-for-data-centers/>)

Author: Ryan Nelson (InfluxData)

Published: 2026-11-03T06:00:00Z

Content type: article

Language: en

Sources: [InfluxData](<https://devfeed.tech/sources/influxdata.md>)

Topics: [streaming data analytics](<https://devfeed.tech/topics/streaming-data-analytics.md>), [data centers](<https://devfeed.tech/topics/data-centers.md>), [big-data](<https://devfeed.tech/topics/big-data.md>), [Data pipelines](<https://devfeed.tech/topics/data-pipelines.md>), [atlassian automated rca](<https://devfeed.tech/topics/atlassian-automated-rca.md>), [data](<https://devfeed.tech/topics/data.md>), [Post Mortem](<https://devfeed.tech/topics/post-mortem.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [ai](<https://devfeed.tech/tags/ai.md>), [alarm](<https://devfeed.tech/tags/alarm.md>), [all](<https://devfeed.tech/tags/all.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [battery](<https://devfeed.tech/tags/battery.md>), [bill](<https://devfeed.tech/tags/bill.md>), [can](<https://devfeed.tech/tags/can.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [capture](<https://devfeed.tech/tags/capture.md>), [cause](<https://devfeed.tech/tags/cause.md>), [cooling](<https://devfeed.tech/tags/cooling.md>), [cost](<https://devfeed.tech/tags/cost.md>), [data](<https://devfeed.tech/tags/data.md>), [data-center](<https://devfeed.tech/tags/data-center.md>), [data-centers](<https://devfeed.tech/tags/data-centers.md>), [demand](<https://devfeed.tech/tags/demand.md>), [developer](<https://devfeed.tech/tags/developer.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [root](<https://devfeed.tech/tags/root.md>), [root-cause-analysis](<https://devfeed.tech/tags/root-cause-analysis.md>)

### AI overview

The article argues that data center root cause analysis slows down when teams manually reconcile timestamps across separate DCIM, BMS, and EPMS systems. It proposes using Telegraf to collect telemetry into InfluxDB 3 Enterprise, attaching asset, location, and customer context as tags so readings from each site share a real-time timeline; InfluxDB Cloud supports fleet-wide comparisons. The stated requirements include high-resolution data, complete readings, contextual metadata, and interoperability through SQL and open APIs. It also describes using the InfluxDB MCP server to give Claude live telemetry for AI-assisted triage and using the same timestamped history to investigate customer billing disputes. The text recommends starting with one site and an Enterprise trial. Its claims describe the proposed product workflow; no independent evaluation is provided.

### Source excerpt

Why RCA takes so long in a modern data center A GPU server started running hot, and the DCIM threw up the first alarm, followed by the BMS reporting a cooling unit failure and the EPMS logging a power dip. Unfortunately, none of the three alarms alerted the team that these incidents happened in tandem. To work out which came first, a tech opens every system, exports data, and lines up the timestamps by hand. If you work in data center operations, you've probably been the one lining up those timestamps, or the one waiting on them. The data that explained that incident was already sitting in all three systems before anyone went looking; the slow part was getting three systems' records into one place, in the right order. Keeping cooling, power, and IT in separate systems makes sense, because the BMS, EPMS, and DCIM were each built for one part of the facility. A single incident, though, shows up in all three at the same time, and each system holds one key part of the story. Today, finding the root cause means hunting down those parts and stitching the records together by hand. That stitching is one of the largest points of cost runaway during an outage. In Uptime Institute's 2025 annual survey, 57% of respondents said their most recent major outage cost more than $100,000. Nobody can start the fix until they know what failed first, so every minute spent reconciling timestamps adds another minute of outage, and the cost keeps climbing. AI is compounding those stitching difficulties as demand pushes data centers to get bigger, denser, and more distributed, adding three new pressures on the data behind root cause analysis: Volume grows with every rack, sensor, and power source a facility adds. Where grid capacity is constrained, operators are adding on-site generation and battery storage, each with its own telemetry stream. Velocity rises with throughput. More demand means more hardware to track, more readings to capture, and more usage to bill, while denser AI racks leav

## Telegraf Enterprise & Controller 1.2: Know Your Fleet's Security Exposure, Versions, and Health

DevFeed: [Telegraf Enterprise & Controller 1.2: Know Your Fleet's Security Exposure, Versions, and Health](<https://devfeed.tech/articles/telegraf-enterprise-controller-1-2-know-your-fleet-s-security-exposure-versions-and-health-104117.md>)

Original publisher: [Read original article](<https://www.influxdata.com/blog/telegraf-enterprise-controller-1-2/>)

Author: Scott Anderson (InfluxData)

Published: 2026-10-27T07:30:00Z

Content type: release

Language: en

Sources: [InfluxData](<https://devfeed.tech/sources/influxdata.md>)

Topics: [infrastructure monitoring](<https://devfeed.tech/topics/infrastructure-monitoring.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>), [Security](<https://devfeed.tech/topics/security.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [air-gapped](<https://devfeed.tech/tags/air-gapped.md>), [also](<https://devfeed.tech/tags/also.md>), [audit](<https://devfeed.tech/tags/audit.md>), [automated](<https://devfeed.tech/tags/automated.md>), [can](<https://devfeed.tech/tags/can.md>), [column](<https://devfeed.tech/tags/column.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [control](<https://devfeed.tech/tags/control.md>), [control-plane](<https://devfeed.tech/tags/control-plane.md>), [controller](<https://devfeed.tech/tags/controller.md>), [counts](<https://devfeed.tech/tags/counts.md>), [data](<https://devfeed.tech/tags/data.md>), [deployments](<https://devfeed.tech/tags/deployments.md>), [developer](<https://devfeed.tech/tags/developer.md>), [docker](<https://devfeed.tech/tags/docker.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [fleet](<https://devfeed.tech/tags/fleet.md>), [health](<https://devfeed.tech/tags/health.md>), [product](<https://devfeed.tech/tags/product.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

Telegraf Controller 1.2 adds tools to assess and maintain Telegraf fleets. Telegraf Enterprise compares agents' heartbeat-reported versions with published advisory ranges, showing exposure by severity and affected agents; air-gapped deployments can import a signed advisory file. Heartbeats can include runtime statistics and recent logs, with error, warning, and metric counts charted over the last 24 heartbeats and logs from the latest heartbeat; enable these by adding `statistics` and `logs` to the heartbeat plugin's `include` list. Fleet views summarize agent status, health, versions, and reporting recency. A heartbeat health indicator and API endpoint expose database, token-cache, and scheduler status. The release also adds token and proxy-IP options and an official Docker image. The supplied source excerpt ends during the agent telemetry instructions, so it does not provide further implementation detail for those other additions.

### Source excerpt

Telegraf Controller 1.2 is now available. It adds security advisory scanning (Telegraf Enterprise), agent-level heartbeat metrics and logs, fleet summary visualizations, and an official Telegraf Controller Docker image. Telegraf Controller is a centralized control plane for managing, configuring, and monitoring your fleet of Telegraf agents. After configuration, the work shifts to maintaining your fleet, and new questions become important: What version of Telegraf are agents using? Which agents are logging errors? Which agents are exposed to the security advisory published this morning? Telegraf Controller 1.2 addresses these questions directly with enhancements and quality-of-life improvements. Security advisory scanning (Telegraf Enterprise) InfluxData publishes security advisories for Telegraf and Telegraf Controller. Controller uses the published advisories to identify what agents are potentially affected by comparing each advisory's affected version ranges against the Telegraf version each agent reports in its heartbeat. A new Security page shows fleet-wide exposure by severity and the agents each advisory affects. The Agents page gains an Advisories column and exposure filter. When a security reviewer asks whether the fleet is exposed, the answer is a filtered list of agents and versions, not a manual audit. Air-gapped deployments can manually import the signed advisory file and still leverage the automated agent advisory scan. For more information, see the Security advisories documentation. Agent-level metrics, errors, and logs Each heartbeat can now carry runtime statistics and a sample of recent Telegraf logs. The updated agent detail page shows error, warning, and metric counts charted across the last 24 heartbeats. You can also inspect log entries from the latest heartbeat. When an agent stops delivering data, you can see when the errors started and read the output plugin error behind the gap without shell access to the host. To enable it, add statistics

## Data Center Telemetry in the AI Era

DevFeed: [Data Center Telemetry in the AI Era](<https://devfeed.tech/articles/data-center-telemetry-in-the-ai-era-97279.md>)

Original publisher: [Read original article](<https://www.influxdata.com/blog/data-center-telemetry/>)

Author: Charles Mahler (InfluxData)

Published: 2026-10-23T08:00:00Z

Content type: article

Language: en

Sources: [InfluxData](<https://devfeed.tech/sources/influxdata.md>)

Topics: [infrastructure monitoring](<https://devfeed.tech/topics/infrastructure-monitoring.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [gpu monitoring](<https://devfeed.tech/topics/gpu-monitoring.md>), [High-Performance Computing](<https://devfeed.tech/topics/high-performance-computing.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-workloads](<https://devfeed.tech/tags/ai-workloads.md>), [automation](<https://devfeed.tech/tags/automation.md>), [data-center](<https://devfeed.tech/tags/data-center.md>), [developer](<https://devfeed.tech/tags/developer.md>), [power](<https://devfeed.tech/tags/power.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>), [use-cases](<https://devfeed.tech/tags/use-cases.md>)

### AI overview

AI data center telemetry needs to align facility, hardware, network, and job data because cooling drift, power swings, and slow or failing GPUs can appear in different systems. The excerpt proposes collecting across those layers on a shared clock and in one store, with sampling matched to the signal: around one second for GPU and rack power where needed, and 15-60 seconds for many other signals. Fast protective controls should remain local; telemetry supports actions from seconds to minutes and longer-term planning. Telegraf collects through existing exporters and read-only facility paths, while Telegraf Controller centralizes agent configuration, staged rollouts, health checks, and resolution profiles. InfluxDB 3 is presented for high-cardinality time series and long-term history in object storage, with SQL or InfluxQL queries and optional self-hosting. The article's examples include correlating power swings with training jobs, spotting GPU and cooling issues, and reviewing SLA or billing events. The excerpt also notes tradeoffs: high-resolution collection costs more, facility networks are segmented, and the free Controller tier covers up to 100 agents and 20 configurations.

### Source excerpt

A decade ago, a typical enterprise rack drew five to ten kilowatts and was cooled by air. Today, reference designs for liquid-cooled AI racks run up to 132 kW per rack, and a large training cluster can swing a facility's power draw by megawatts in a few seconds. More than half of operators in Uptime Institute's 2026 survey built or upgraded high-density space in the past year, and 70% plan to in the next year as well. The entire industry is changing as AI-focused workloads become more common. Telemetry is how operators see what all that hardware is doing. Most data centers already collect a great deal of it. The trouble is that this data lives in different systems, at different resolutions, with different clocks, owned by different teams. In a data center running AI workloads, where a cooling problem can surface as a slow training job, that fragmentation makes problems difficult to trace. Handling this new set of problems requires a different approach and different tools. What is data center telemetry? Data center telemetry is the continuous, time-stamped measurement of every layer of a data center, from the utility feed to the training job. It is used for three things: Monitoring: dashboards, threshold alerts, and on-call response Automation: actions taken on the data, like draining an unhealthy node or flagging a rack whose coolant flow is drifting Planning: capacity, power provisioning, forecasting, hardware replacement, and contract evidence, all built on history It helps to think of telemetry in seven layers. The first three belong to the facility (operational technology, or OT). The last four belong to the IT stack. Layer Signals Sources Power Utility feeds, switchgear, UPS state of charge and battery health, and PDU branch-circuit load EPMS, power meters, SNMP, Modbus Cooling Supply and return temperatures, chilled water, CDU flow, pressure, leak detection, coolant conductivity BMS, SCADA Environment Rack inlet temperature, humidity, differential pressure, ai

## Root Cause Analysis Workflows Using InfluxDB

DevFeed: [Root Cause Analysis Workflows Using InfluxDB](<https://devfeed.tech/articles/root-cause-analysis-workflows-using-influxdb-87386.md>)

Original publisher: [Read original article](<https://www.influxdata.com/blog/root-cause-analysis-workflows-influxdb/>)

Author: Community (InfluxData)

Published: 2026-10-14T08:00:00Z

Content type: tutorial

Language: en

Sources: [InfluxData](<https://devfeed.tech/sources/influxdata.md>)

Topics: [reliability-engineering](<https://devfeed.tech/topics/reliability-engineering.md>), [Time Series](<https://devfeed.tech/topics/time-series.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>)

Tags: [developer](<https://devfeed.tech/tags/developer.md>), [distributed-system](<https://devfeed.tech/tags/distributed-system.md>), [influxdb](<https://devfeed.tech/tags/influxdb.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [root-cause-analysis](<https://devfeed.tech/tags/root-cause-analysis.md>)

### AI overview

The tutorial presents a four-step InfluxDB workflow for investigating production incidents: establish the incident timeline and baseline, correlate latency, traffic, errors and saturation, isolate affected infrastructure using tags, and examine potential causes through timing and proportionality. SQL examples illustrate metric alignment, container-level analysis and changes in database connections.

### Source excerpt

It's 2:00 AM, and your monitoring system fires a critical alert. Latency is spiking, and overseas users are registering internal server error complaints. How quickly can you find the root problem? Your logs and relational databases hold plenty of data about what's happening. But it's difficult, if not downright impossible, to coerce that information into a timeline that will help you figure out what's happening. Establishing an accurate sequence of events is a key step in root cause analysis (RCA), and that's where InfluxDB comes in. It excels at collecting, storing, and querying high-resolution, time-stamped metrics. These abilities make InfluxDB the ideal tool for reconstructing the scene of an operational crime and finding the definitive cause of an incident. Let's see how. What is Root Cause Analysis? Before we start, let's make sure we're all on the same page. __Root cause analysis is a structured methodology for identifying the core cause of an issue, failure, or unexpected event. __ RCA uncovers why a problem occurred in the first place, ensuring you can prevent it from happening again. It's not uncommon for the components in a distributed system to literally and figuratively speak different languages. Time series data is the foundation of RCA It's not uncommon for the components in a distributed system to literally and figuratively speak different languages. Your API gateway might be written in Go, while you're using an off-the-shelf authorization service that's implemented in Node.js. At the same time, you might have a mix of backend workers running in Python and Java. So when a critical incident strikes, they're logging messages in different languages, using different terminology, and generating stack traces that look like they're from different worlds. But no matter how many dialects your services speak, they share one property you can take advantage of: time. Causality is the key to RCA. You need to prove that event A caused event B. When time is the anc

## Telegraf Socket Listener Plugin: UDP, TCP and Unix Sockets

DevFeed: [Telegraf Socket Listener Plugin: UDP, TCP and Unix Sockets](<https://devfeed.tech/articles/telegraf-socket-listener-plugin-udp-tcp-and-unix-sockets-88341.md>)

Original publisher: [Read original article](<https://www.influxdata.com/blog/telegraf-socket-listener-input-plugin/>)

Author: Noah Crowley (InfluxData)

Published: 2026-10-09T07:00:00Z

Content type: tutorial

Language: en

Sources: [InfluxData](<https://devfeed.tech/sources/influxdata.md>)

Topics: [infrastructure monitoring](<https://devfeed.tech/topics/infrastructure-monitoring.md>), [WebSocket](<https://devfeed.tech/topics/websocket.md>), [Website](<https://devfeed.tech/topics/website.md>), [TCP/IP](<https://devfeed.tech/topics/tcp-ip.md>)

Tags: [developer](<https://devfeed.tech/tags/developer.md>), [influxdb](<https://devfeed.tech/tags/influxdb.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [product](<https://devfeed.tech/tags/product.md>), [tcp](<https://devfeed.tech/tags/tcp.md>), [udp](<https://devfeed.tech/tags/udp.md>), [unix](<https://devfeed.tech/tags/unix.md>), [use-cases](<https://devfeed.tech/tags/use-cases.md>)

### AI overview

The article shows how to use Telegraf's socket_listener input plugin to send data into Telegraf and InfluxDB over UDP and Unix sockets. It explains UDP's delivery and overhead tradeoffs, configures a UDP listener on port 8094, and demonstrates sending and verifying points. It then shows a Python script that writes random walk data through a Unix datagram socket, noting that Unix sockets can reduce local communication overhead.

### Source excerpt

One of Telegraf's biggest strengths is the large collection of plugins it offers that can be used to immediately start collecting data from a variety of applications. This covers a lot of common infrastructure components like databases and web servers, but if you want to get data into Telegraf using your own scripts or applications, there are also a variety of more general-purpose input plugins that you can use. There's a file plugin, which will read from or tail a file on disk, an exec plugin which will execute your own scripts or commands and parse their output, and plugins to listen for data via HTTP or poll external endpoints (http_listener_v2 and http). One of the plugins I end up using most often is the socket_listener plugin, which allows you to send data to Telegraf using UDP, TCP, or Unix sockets. The simplicity of InfluxDB's line protocol and the ease with which you can write to a socket using most programming languages makes this a powerful tool for both quick prototyping and more long-term solutions. Let's take a look at some examples of the plugin in action. We'll use a host system running Ubuntu, with Telegraf and InfluxDB installed from the official InfluxData repository. UDP: User Datagram Protocol For this first example, let's configure the socket_listener plugin to accept UDP packets. The UDP protocol is a connectionless, best-effort service: messages are sent to their recipient with no guarantee that they will be received. One benefit of this is that it means there is less processing overhead for UDP relative to something like TCP, which is more reliable. That makes UDP well-suited for things like interprocess communication or situations in which some loss of data is acceptable. In order to set up Telegraf to receive UDP messages, first configure this block in your telegraf.conf: [[inputs.socket_listener]] service_address = "udp://:8094" data_format = "influx" This configures Telegraf to listen for data on UDP port 8094 in InfluxDB line protocol f

## The Complete Guide to Writing Data to InfluxDB with Python

DevFeed: [The Complete Guide to Writing Data to InfluxDB with Python](<https://devfeed.tech/articles/the-complete-guide-to-writing-data-to-influxdb-with-python-87387.md>)

Original publisher: [Read original article](<https://www.influxdata.com/blog/writing-data-to-influxdb-with-python/>)

Author: Noah Crowley (InfluxData)

Published: 2026-10-08T09:45:00Z

Content type: tutorial

Language: en

Sources: [InfluxData](<https://devfeed.tech/sources/influxdata.md>)

Topics: [Python](<https://devfeed.tech/topics/python.md>)

Tags: [batch](<https://devfeed.tech/tags/batch.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [client-library](<https://devfeed.tech/tags/client-library.md>), [command-line](<https://devfeed.tech/tags/command-line.md>), [database](<https://devfeed.tech/tags/database.md>), [developer](<https://devfeed.tech/tags/developer.md>), [influxdb](<https://devfeed.tech/tags/influxdb.md>), [performance](<https://devfeed.tech/tags/performance.md>), [product](<https://devfeed.tech/tags/product.md>), [python](<https://devfeed.tech/tags/python.md>), [use-cases](<https://devfeed.tech/tags/use-cases.md>)

### AI overview

This tutorial explains ways to improve write performance when using the InfluxDB Python client library. It demonstrates measuring the write operation with Python's performance counter, using InfluxDB Line Protocol instead of JSON, and batching writes. The examples report faster insertion with Line Protocol and batch sizes of 5,000-10,000 points, and recommend examining system resources and I/O when performance remains slow.

### Source excerpt

One of the questions we see fairly often from Python developers who are using InfluxDB is how to improve the write performance of programs that use the InfluxDB client library. Usually, they're trying to import or transfer large amounts of data and want to make sure it can be inserted into the database quickly enough for their business needs. In this post, we'll go over the common pitfalls that people encounter, as well as some performance best practices. The script Let's look at an example of a Python script that writes data to InfluxDB. You can find it here. The first part of the script (up until Line 56) is used for creating the data we'll use to populate our measurements; there is a list of locations, a list of fruits, and a function that generates 1000 UUIDs. We create an array and append the first value to it using our data as follows: data = [] data.append("{measurement},location={location},fruit={fruit},id={id} x={x},y={y},z={z}i {timestamp}" .format(measurement=measurement_name, location=random.choice(location_tags), fruit=random.choice(fruit_tags), id=random.choice(id_tags), x=round(random.random(),4), y=round(random.random(),4), z=random.randint(0,50), timestamp=data_start_time)) This will append a string that looks like: m1,location=location,fruit=fruit,id=id x=10,y=1,z=42i 1562458785618 At the beginning of the script, we defined a variable that contains the number of points we'd like to write: in this case, 250,000. Once that data has been generated and loaded into the array, we can write it to the database as follows: client.write_points(data, database='python-throughput', time_precision='ms', batch_size=10000, protocol='line') Measuring performance Most Unix systems have some version of the time command, which measures the amount of time it takes for a process to execute and then prints it to the command line. $ time echo "hello world" hello world real 0m0.000s user 0m0.000s sys 0m0.000s It's a tool that many Linux users are familiar with, but the iss

## Q3 2026 Recap: Up to 4x Faster Single-Series Queries, Distributed Compaction, and Telegraf High Availability

DevFeed: [Q3 2026 Recap: Up to 4x Faster Single-Series Queries, Distributed Compaction, and Telegraf High Availability](<https://devfeed.tech/articles/q3-2026-recap-up-to-4x-faster-single-series-queries-distributed-compaction-and-telegraf-high-availability-66490.md>)

Original publisher: [Read original article](<https://www.influxdata.com/blog/q3-recap-influxdb/>)

Author: Ryan Nelson (InfluxData)

Published: 2026-10-07T08:00:00Z

Content type: news

Language: en

Sources: [InfluxData](<https://devfeed.tech/sources/influxdata.md>)

Topics: [Distributed Systems & Parallel Computing](<https://devfeed.tech/topics/distributed-systems-parallel-computing.md>), [Data pipelines](<https://devfeed.tech/topics/data-pipelines.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [gRPC](<https://devfeed.tech/topics/grpc.md>)

Tags: [amazon-timestream](<https://devfeed.tech/tags/amazon-timestream.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [databases](<https://devfeed.tech/tags/databases.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [high-availability](<https://devfeed.tech/tags/high-availability.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [parquet](<https://devfeed.tech/tags/parquet.md>), [performance](<https://devfeed.tech/tags/performance.md>), [product](<https://devfeed.tech/tags/product.md>), [rbac](<https://devfeed.tech/tags/rbac.md>), [release](<https://devfeed.tech/tags/release.md>)

### AI overview

The Q3 2026 recap covers releases for InfluxDB, Amazon Timestream for InfluxDB, and Telegraf. It highlights faster selective queries and data-management features in InfluxDB, AWS IoT Core ingestion and Python plugins for Timestream, and high availability and fleet management updates for Telegraf.

### Source excerpt

InfluxDB 3.11 brings performance for heavier, more complex workloads to GA When a system acts on a device's latest reading or an asset's current state, query speed decides how fast it can respond, and that gets harder as devices multiply and schemas widen. InfluxDB 3.11, released July 30, made performance improvements built for exactly those workloads in InfluxDB 3 Enterprise. For highly selective queries, like those for a single time series, this release is 4X faster than previous Enterprise 3 releases. Teams modeling sensor fleets or satellite telemetry can now design schemas around their data, with support for thousands of tables, millions of columns, and ultra-sparse datasets. Memory use also stays steadier under heavy ingest, which makes infrastructure easier to size. Three new Enterprise capabilities make it safer to protect and clean up production data: Backup and restore: full or incremental backups, with asynchronous restores that can roll a live cluster back to an earlier point when you need to Bulk import from Parquet: ingest an entire directory of Parquet files directly Row-level deletes: remove data by time range or tag predicate without dropping a table The built-in Explorer UI puts all of this within reach. Teams can query in SQL, InfluxQL, or natural language, convert existing Flux queries to SQL, and manage Processing Engine plugins, all from one unified location. InfluxDB 3.12 gives growing deployments more capacity and more control A deployment that's working tends to attract more of everything: months of backfill, bursty ingest, and more teams writing to the same databases. InfluxDB 3.12 gives operators new ways to handle all of it, and is exclusive to InfluxDB 3 Enterprise. With RBAC now GA in InfluxDB 3.12, admins manage users, sign-in methods, and roles from one screen Amazon Timestream for InfluxDB shortens the path from device to database on AWS For teams building on AWS, device data now has a much shorter trip into InfluxDB. AWS shipped thr

## How to Write Logs Directly to InfluxDB: A Complete Guide

DevFeed: [How to Write Logs Directly to InfluxDB: A Complete Guide](<https://devfeed.tech/articles/how-to-write-logs-directly-to-influxdb-a-complete-guide-86948.md>)

Original publisher: [Read original article](<https://www.influxdata.com/blog/writing-logs-directly-to-influxdb/>)

Author: Noah Crowley (InfluxData)

Published: 2026-10-05T11:35:00Z

Content type: tutorial

Language: en

Sources: [InfluxData](<https://devfeed.tech/sources/influxdata.md>)

Topics: [telemetry](<https://devfeed.tech/topics/telemetry.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>), [Structured-data](<https://devfeed.tech/topics/structured-data.md>)

Tags: [debugging](<https://devfeed.tech/tags/debugging.md>), [developer](<https://devfeed.tech/tags/developer.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [influxdb](<https://devfeed.tech/tags/influxdb.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [product](<https://devfeed.tech/tags/product.md>), [use-cases](<https://devfeed.tech/tags/use-cases.md>)

### AI overview

The article explains how to write syslog-shaped log points directly to InfluxDB so they appear in Chronograf's Log Viewer, without running syslog or the Telegraf plugin. It describes the expected schema, gives line protocol examples, and recommends batching points to avoid overwhelming the database with individual HTTP requests.

### Source excerpt

Back in June, we published a blog on our "metrics-first" approach to log analysis; we had found that just over a quarter of our users were already using the InfluxData platform for storing logs and non-numerical events. We consider logs to be just another form of time series data, and so we wanted to give those users better tools for ingesting and viewing that data. At the end of the day, logs are extremely valuable for debugging and troubleshooting; they provide detailed insight into the goings-on of your systems, and let you explore problems in ways that predefined dashboards don't allow. We released a plugin for Telegraf that allows you to ingest logs using the syslog protocol, which was based on work we were doing internally, and then back in July, we added log viewing functionality to Chronograf. If you're interested in getting rsyslog and the Telegraf plugin up and running on macOS or Linux, you should check out the Get Your Syslog On blog post. Once you start writing data, you'll be able to explore it through the Log Viewer panel in Chronograf. Not everyone wants to run a syslog instance, however, and we've gotten a few questions here and there about how to write logs directly to InfluxDB so that they can be viewed in Chronograf, but without using syslog or the Telegraf plugin. Good news! This is totally possible! First, let's dig a little deeper into the implementation so we can understand what's really going on. The first thing to understand is that syslog is a protocol; it describes how messages should be formatted and transmitted. This is described in RFC5424 - The Syslog Protocol. Part of that specification includes details on how to use structured data in your logs, which we strongly encourage! When you're using syslog and Telegraf, the latter is responsible for accepting messages in syslog format and converting them to line protocol to be written to InfluxDB. It inserts all syslog messages into a measurement called syslog, which is what Chronograf look

## Why Automotive Manufacturers Are Augmenting Data Historians, Not Replacing Them

DevFeed: [Why Automotive Manufacturers Are Augmenting Data Historians, Not Replacing Them](<https://devfeed.tech/articles/why-automotive-manufacturers-are-augmenting-data-historians-not-replacing-them-64699.md>)

Original publisher: [Read original article](<https://www.influxdata.com/blog/why-auto-manufacturers-augment-historians/>)

Author: Ryan Nelson (InfluxData)

Published: 2026-10-05T08:00:00Z

Content type: article

Language: en

Sources: [InfluxData](<https://devfeed.tech/sources/influxdata.md>)

Topics: [Data pipelines](<https://devfeed.tech/topics/data-pipelines.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [data](<https://devfeed.tech/topics/data.md>)

Tags: [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-native](<https://devfeed.tech/tags/cloud-native.md>), [data](<https://devfeed.tech/tags/data.md>), [developer](<https://devfeed.tech/tags/developer.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [influxdb](<https://devfeed.tech/tags/influxdb.md>), [instrumentation](<https://devfeed.tech/tags/instrumentation.md>), [use-cases](<https://devfeed.tech/tags/use-cases.md>)

### AI overview

Automotive manufacturers are adding sensors and collecting more high-frequency factory telemetry, while traditional data historians can become costly to expand and difficult to scale across plants. The article describes augmenting existing historians with InfluxDB: routing new telemetry to it for dashboards, anomaly detection and predictive maintenance, or consolidating data from separate historians. It also discusses using Telegraf or Litmus for data collection and integration.

### Source excerpt

A modern vehicle assembly line generates more time-stamped telemetry before lunch than most data historians were built to hold: weld temperatures, torque readings, and vibration traces from every robot, torque tool, vision system, and test stand, and on most historians, each signal carries its own line-item cost because the systems are still priced per tag. That model was fine when data was scarce; it breaks down as OEMs and Tier 1 and Tier 2 suppliers add sensors, stations, and higher sampling rates every year, turning instrumentation into a budgeting exercise before it becomes a visibility gain. The instinct is to rip out the historian and start over. On a validated, IATF 16949-certified production line, that's rarely realistic: historians from vendors like OSI PI/AVEVA, Wonderware, GE, and Honeywell are wired into SCADA systems, PLCs, robot controllers, and distributed control systems that keep the line running, and replacing that layer risks a stoppage that cascades into missed takt, JIT penalties, and downstream OEM shutdowns within hours. InfluxDB, a purpose-built time series platform, takes a more pragmatic path: augmenting the historian instead of replacing it. Why data historians are hitting a wall in Industry 4.0 Data historians were built for Industry 3.0: one plant, one shift pattern, one set of tags, running on-premises with modest data volumes. They're still good at that job. What they weren't built for is Industry 4.0, where interconnected devices, IIoT sensors, and cloud-native systems generate volume, variety, and velocity of telemetry that legacy architectures never had to handle. Three problems show up consistently as manufacturers try to close that gap. Vendor lock-in. Historians are proprietary and tightly controlled by their vendors. Licensing, upgrades, and even adding a tag for a new robot sensor or launch program often require vendor involvement, which locks plants into a single roadmap at a time when margins are already under tariff and EV-

## What's New in InfluxDB 3.12: Distributed Compaction, 3x Faster Imports, and More Control

DevFeed: [What's New in InfluxDB 3.12: Distributed Compaction, 3x Faster Imports, and More Control](<https://devfeed.tech/articles/what-s-new-in-influxdb-3-12-distributed-compaction-3x-faster-imports-and-more-control-63343.md>)

Original publisher: [Read original article](<https://www.influxdata.com/blog/influxdb-3-12/>)

Author: Peter Barnett (InfluxData)

Published: 2026-10-01T08:20:00Z

Content type: release

Language: en

Sources: [InfluxData](<https://devfeed.tech/sources/influxdata.md>)

Topics: [Scapy](<https://devfeed.tech/topics/scapy.md>), [database-optimization](<https://devfeed.tech/topics/database-optimization.md>), [Distributed Systems & Parallel Computing](<https://devfeed.tech/topics/distributed-systems-parallel-computing.md>), [consistency](<https://devfeed.tech/topics/consistency.md>)

Tags: [database](<https://devfeed.tech/tags/database.md>), [developer](<https://devfeed.tech/tags/developer.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [faster](<https://devfeed.tech/tags/faster.md>), [influxdb](<https://devfeed.tech/tags/influxdb.md>), [news](<https://devfeed.tech/tags/news.md>), [performance](<https://devfeed.tech/tags/performance.md>), [product](<https://devfeed.tech/tags/product.md>), [production](<https://devfeed.tech/tags/production.md>), [schema](<https://devfeed.tech/tags/schema.md>), [schemas](<https://devfeed.tech/tags/schemas.md>)

### AI overview

InfluxDB 3.12 adds faster parallel Parquet imports, beta distributed compaction, per-database schema enforcement, and generally available role-based access control in InfluxDB 3 Enterprise. The release also updates the Explorer UI and Processing Engine deployment options.

### Source excerpt

Time series deployments rarely grow the way they were planned. A single-node pilot becomes a multi-node fleet, an afternoon's worth of test data becomes weeks of backfill that has to land before anyone can query it, and three teams end up writing to a database built for one. InfluxDB 3.11 delivered a higher-performance foundation for complex time series workloads, with significant performance improvements for single-series queries, schemas that could go wide and sparse without breaking, and a much more predictable resource profile. For InfluxDB 3 Enterprise, 3.12 builds on that foundation with more ways to scale operations around those workloads. Bulk imports make better use of available CPU, compaction can now scale across nodes, and schema enforcement gives teams more control over shared production datasets. The common thread is simple: as the workload grows, more of the system can grow with it. Bulk import, now 3x faster Historical data isn't useful until it's queryable. When you're migrating to InfluxDB or backfilling months of history, import speed decides how soon that data sits alongside your live data, whether that's by lunch or next week. InfluxDB 3.12 makes bulk import from Parquet roughly three times faster. Imports now run in parallel, so they scale with the hardware you give them. In testing, import time fell by 64-70 percent across workloads. Imports are also easier to lock down. Bulk import no longer requires an admin token. It now authorizes against write permission on the target database, so the credential running a backfill only needs access to the data it's loading. Distributed compaction, now in beta Compaction keeps queries fast by organizing newly written data into efficient files in the background. At high ingest volumes, though, that background work can become the bottleneck: compaction falls behind, and the only fix is a bigger machine. InfluxDB 3.12 removes that ceiling. With distributed compaction, now in beta, compaction becomes something

## What's New in InfluxDB 3.12: Distributed Compaction, 3x Faster Imports, and More Control

DevFeed: [What's New in InfluxDB 3.12: Distributed Compaction, 3x Faster Imports, and More Control](<https://devfeed.tech/articles/what-s-new-in-influxdb-3-12-distributed-compaction-3x-faster-imports-and-more-control-63010.md>)

Original publisher: [Read original article](<https://www.influxdata.com/blog/whats-new-influxdb-3-1-2/>)

Author: Peter Barnett (InfluxData)

Published: 2026-10-01T07:48:31.577321Z

Content type: release

Language: en

Sources: [InfluxData](<https://devfeed.tech/sources/influxdata.md>)

Topics: [Distributed Systems & Parallel Computing](<https://devfeed.tech/topics/distributed-systems-parallel-computing.md>), [database-optimization](<https://devfeed.tech/topics/database-optimization.md>), [Amazon DynamoDB](<https://devfeed.tech/topics/amazon-dynamodb.md>)

Tags: [builds](<https://devfeed.tech/tags/builds.md>), [data](<https://devfeed.tech/tags/data.md>), [database](<https://devfeed.tech/tags/database.md>), [deployments](<https://devfeed.tech/tags/deployments.md>), [developer](<https://devfeed.tech/tags/developer.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [news](<https://devfeed.tech/tags/news.md>), [permission](<https://devfeed.tech/tags/permission.md>), [product](<https://devfeed.tech/tags/product.md>), [production](<https://devfeed.tech/tags/production.md>), [scale](<https://devfeed.tech/tags/scale.md>), [time-series](<https://devfeed.tech/tags/time-series.md>)

### AI overview

InfluxDB 3.12 adds roughly three times faster parallel Parquet imports, beta distributed compaction that can scale across nodes, and per-database schema enforcement. The release also introduces generally available role-based access control for InfluxDB 3 Enterprise and lets imports use write permissions instead of an admin token.

### Source excerpt

Time series deployments rarely grow the way they were planned. A single-node pilot becomes a multi-node fleet, an afternoon's worth of test data becomes weeks of backfill that has to land before anyone can query it, and three teams end up writing to a database built for one. InfluxDB 3.11 delivered a higher-performance foundation for complex time series workloads, with significant performance improvements for single-series queries, schemas that could go wide and sparse without breaking, and a much more predictable resource profile. For InfluxDB 3 Enterprise, 3.12 builds on that foundation with more ways to scale operations around those workloads. Bulk imports make better use of available CPU, compaction can now scale across nodes, and schema enforcement gives teams more control over shared production datasets. The common thread is simple: as the workload grows, more of the system can grow with it. Bulk import, now 3x faster Historical data isn't useful until it's queryable. When you're migrating to InfluxDB or backfilling months of history, import speed decides how soon that data sits alongside your live data, whether that's by lunch or next week. InfluxDB 3.12 makes bulk import from Parquet roughly three times faster. Imports now run in parallel, so they scale with the hardware you give them. In testing, import time fell by 64-70 percent across workloads. Imports are also easier to lock down. Bulk import no longer requires an admin token. It now authorizes against write permission on the target database, so the credential running a backfill only needs access to the data it's loading. Distributed compaction, now in beta Compaction keeps queries fast by organizing newly written data into efficient files in the background. At high ingest volumes, though, that background work can become the bottleneck: compaction falls behind, and the only fix is a bigger machine. InfluxDB 3.12 removes that ceiling. With distributed compaction, now in beta, compaction becomes something

## Telegraf 1.40 Release Notes

DevFeed: [Telegraf 1.40 Release Notes](<https://devfeed.tech/articles/telegraf-1-40-release-notes-56907.md>)

Original publisher: [Read original article](<https://www.influxdata.com/blog/telegraf-1-40-release-notes-influxdb/>)

Author: Sven Rebhan (InfluxData)

Published: 2026-09-15T00:00:00Z

Content type: release

Language: en

Sources: [InfluxData](<https://devfeed.tech/sources/influxdata.md>)

Topics: [Release notes](<https://devfeed.tech/topics/release-notes.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [databricks](<https://devfeed.tech/topics/databricks.md>), [deprecated](<https://devfeed.tech/topics/deprecated.md>), [elasticsearch](<https://devfeed.tech/topics/elasticsearch.md>), [migration](<https://devfeed.tech/topics/migration.md>), [Cisco](<https://devfeed.tech/topics/cisco.md>), [gRPC](<https://devfeed.tech/topics/grpc.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [cisco](<https://devfeed.tech/tags/cisco.md>), [databricks](<https://devfeed.tech/tags/databricks.md>), [deprecated](<https://devfeed.tech/tags/deprecated.md>), [developer](<https://devfeed.tech/tags/developer.md>), [elasticsearch](<https://devfeed.tech/tags/elasticsearch.md>), [github](<https://devfeed.tech/tags/github.md>), [grpc](<https://devfeed.tech/tags/grpc.md>), [migrate](<https://devfeed.tech/tags/migrate.md>), [notes](<https://devfeed.tech/tags/notes.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [product](<https://devfeed.tech/tags/product.md>), [release](<https://devfeed.tech/tags/release.md>), [release-notes](<https://devfeed.tech/tags/release-notes.md>)

### AI overview

Telegraf 1.40 adds Databricks Zerobus and Fritzbox Smarthome input plugins, fixes Cisco telemetry metrics, removes deprecated plugins and options, provides configuration migration support, and updates the Elasticsearch query input plugin with support for Elasticsearch v7, v8, and v9.

### Source excerpt

You can find the binaries for the latest Telegraf release on our Downloads page. Many thanks to all the open source community members who contributed to this effort! New plugins These are the newest plugins, first available in this version: Databricks Zerobus output (outputs.zerobus) Streams metrics to a Unity Catalog Delta table using the Databricks Zerobus Ingest service over gRPC to directly commit into Delta Contributed by zlata-stefanovic-db Fritzbox Smarthome input (inputs.fritzbox_smarthome) Reads metrics such as lamp state, energy consumption, etc., from Smarthome-capable FRITZ! routers using the AVM Home Automation interface. Contributed by hdecarne Important changes Here are some changes to highlight: Cisco Model-Driven-Telemetry fixes Several fixes changed the metric format Configured aliases are now respected for microburst and RIB messages, which might result in changes to the metric name Spurious, invalid metrics with wrong tag-sets were removed or corrected Row numbers are now tagged correctly for table messages Smart input fix for power-on-hours Power-on-hours are now reported correctly for raw values in 182h+39m+24.879s format Previously, those values resulted in the field containing the time in seconds Removal of deprecated plugins inputs.aerospike inputs.sflow outputs.amon Removal of deprecated plugin options inputs.kafka_consumer removal of connection_strategy inputs.openstack removal of server_diagnostics inputs.procstat removal of cmdline_tag, pid_tag, and supervisor_unit inputs.tail removal of from_beginning Use the telegraf config migrate command to migrate your configuration Elasticsearch query input plugin migration to official library Migration to official and maintained libraries Additional support for Elasticsearch v7, v8 and v9 Downloads Head to our Downloads page to get the latest Telegraf release. If you have issues or questions, please join our InfluxDB Community Slack or post them in our InfluxDB GitHub Repo or Community Site, and w

## Building a Practical Time Series Data Layer for Automotive Manufacturing

DevFeed: [Building a Practical Time Series Data Layer for Automotive Manufacturing](<https://devfeed.tech/articles/building-a-practical-time-series-data-layer-for-automotive-manufacturing-56910.md>)

Original publisher: [Read original article](<https://www.influxdata.com/blog/time-series-for-auto-manufacturing/>)

Author: Cole Bowden (InfluxData)

Published: 2026-09-09T08:00:00Z

Content type: article

Language: en

Sources: [InfluxData](<https://devfeed.tech/sources/influxdata.md>)

Topics: [Time Series](<https://devfeed.tech/topics/time-series.md>), [Database](<https://devfeed.tech/topics/database.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [DateTime](<https://devfeed.tech/topics/datetime.md>)

Tags: [automotive](<https://devfeed.tech/tags/automotive.md>), [data](<https://devfeed.tech/tags/data.md>), [developer](<https://devfeed.tech/tags/developer.md>), [influxdb](<https://devfeed.tech/tags/influxdb.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [time-series](<https://devfeed.tech/tags/time-series.md>)

### AI overview

The article explains why automotive manufacturing data is a time-series workload and presents InfluxDB as a storage and query layer for continuous, timestamped sensor and production data.

### Source excerpt

Automotive manufacturing generates data at several operating cadences. Sensors and controllers emit measurements continuously. Equipment and line states change as events. Production and quality systems add context at the part, batch, shift, and plant level. Together, these records describe how a manufacturing process behaves over time. That data can support plant visibility, investigations, scrap reduction, condition monitoring, and longer-term comparison, but only if the storage and query layer can keep up with the workload. InfluxDB is a practical fit for these types of workloads because it is optimized for continuous, time-stamped data and can process, retain, and query it without requiring every system around it to be redesigned. Why automotive data is a time series workload A time series workload is, at its core, any data where you primarily store, query, and analyze it by looking at when it happened and how it progressed from one state to another. A temperature measurement in a time series workload never exists in isolation. When a device overheats, you ask how long it took to heat up, whether it had opportunities to cool down, and what that looked like over the span of five, ten, or fifty minutes. The same principles can apply to vibration, torque, current, pressure, flow, cycle state, machine availability, inspection results, alarms, and many other signals generated during vehicle and component production. Queries are written to understand what changed during a particular interval, whether a condition persisted, how one shift compared with another, or how several signals behaved around a production or quality event. Those queries tend to start with a filter on timestamps to the relevant window in which questions are being asked, narrow the data to the relevant equipment or process, and then aggregate, compare, or retrieve the latest values. The write pattern of time series data is often distinctive, too. Sensors create readings at a regular cadence, so new d

## Getting Started with InfluxDB 3 and Grafana Tutorial

DevFeed: [Getting Started with InfluxDB 3 and Grafana Tutorial](<https://devfeed.tech/articles/getting-started-with-influxdb-3-and-grafana-tutorial-56899.md>)

Original publisher: [Read original article](<https://www.influxdata.com/blog/getting-started-influxdb-3-grafana/>)

Author: Charles Mahler (InfluxData)

Published: 2026-09-02T07:00:00Z

Content type: tutorial

Language: en

Sources: [InfluxData](<https://devfeed.tech/sources/influxdata.md>)

Topics: [Grafana](<https://devfeed.tech/topics/grafana.md>), [dashboards](<https://devfeed.tech/topics/dashboards.md>), [Time Series](<https://devfeed.tech/topics/time-series.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [SQL](<https://devfeed.tech/topics/sql.md>), [Python](<https://devfeed.tech/topics/python.md>), [Flight](<https://devfeed.tech/topics/flight.md>)

Tags: [dashboards](<https://devfeed.tech/tags/dashboards.md>), [developer](<https://devfeed.tech/tags/developer.md>), [getting-started](<https://devfeed.tech/tags/getting-started.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [python](<https://devfeed.tech/tags/python.md>), [sql](<https://devfeed.tech/tags/sql.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>), [time-series](<https://devfeed.tech/tags/time-series.md>), [tutorial](<https://devfeed.tech/tags/tutorial.md>)

### AI overview

This tutorial explains how to integrate InfluxDB 3 with Grafana for time-series monitoring. It covers ingesting and transforming data, configuring a read-only Grafana data source, and building dashboards from generated smart-building telemetry.

### Source excerpt

InfluxDB and Grafana are the most common pairing in time series monitoring, and division of labor between them is simple. InfluxDB stores and queries the data: high-volume, time-stamped readings from sensors, servers, meters, vehicles, and anything else that emits time series. Grafana visualizes the data: dashboards, time series panels, stat tiles, state timelines, and alerts. Neither tool replaces the other, and many production monitoring stacks run both. Connecting them has gotten considerably simpler with InfluxDB 3. Grafana ships with a built-in InfluxDB datasource that speaks InfluxDB 3 SQL over Flight SQL, so there is no third-party plugin to install and no custom query language to learn. This guide walks through that integration end-to-end using a realistic dataset you generate yourself. You will learn the following in this tutorial: Getting data in - Writing line protocol and what tags, fields, and timestamps mean for how you will query later. Transforming data as it arrives - Using an InfluxDB 3 Python Processing Engine plugin to turn raw readings into a derived table of decisions. This pattern keeps dashboard queries simple and your source data untouched. Connecting Grafana securely - Read-only tokens and the datasource settings that actually matter. Building a real dashboard - Template variables, chained variables, $__timeFilter, date_bin() for downsampling, and eight panels across stats, time series, state timelines, bar gauges, and tables. What you will build with InfluxDB 3 and Grafana To make all of that concrete, you will generate a week of smart-building data. The generator is deterministic, so your numbers will match the expected output at every step, and you can verify each stage rather than guessing. The raw table, building_telemetry, preserves the original readings. The derived table, iaq_assessment, adds an indoor-air-quality risk score, a severity label, a recommended action, and a conservative estimate of energy used above an idle baseline. T

## Democratizing Breach Detection: How SMBs Can Build Their Own Time Series Security Monitor

DevFeed: [Democratizing Breach Detection: How SMBs Can Build Their Own Time Series Security Monitor](<https://devfeed.tech/articles/democratizing-breach-detection-how-smbs-can-build-their-own-time-series-security-monitor-56905.md>)

Original publisher: [Read original article](<https://www.influxdata.com/blog/smb-security-monitoring-influxdb/>)

Author: Peter Albert, Jamie Strandboge (InfluxData)

Published: 2026-08-27T08:00:00Z

Content type: article

Language: en

Sources: [InfluxData](<https://devfeed.tech/sources/influxdata.md>)

Topics: [Security](<https://devfeed.tech/topics/security.md>), [Time Series](<https://devfeed.tech/topics/time-series.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [observability](<https://devfeed.tech/topics/observability.md>), [audit](<https://devfeed.tech/topics/audit.md>), [Security Information and Event Management (SIEM)](<https://devfeed.tech/topics/siem-security.md>), [dashboards](<https://devfeed.tech/topics/dashboards.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [audit](<https://devfeed.tech/tags/audit.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [breach](<https://devfeed.tech/tags/breach.md>), [dashboards](<https://devfeed.tech/tags/dashboards.md>), [data](<https://devfeed.tech/tags/data.md>), [data-collection](<https://devfeed.tech/tags/data-collection.md>), [detection](<https://devfeed.tech/tags/detection.md>), [monitor](<https://devfeed.tech/tags/monitor.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [observability](<https://devfeed.tech/tags/observability.md>), [practical](<https://devfeed.tech/tags/practical.md>), [product](<https://devfeed.tech/tags/product.md>), [security](<https://devfeed.tech/tags/security.md>), [security-events](<https://devfeed.tech/tags/security-events.md>), [siem](<https://devfeed.tech/tags/siem.md>), [time-series](<https://devfeed.tech/tags/time-series.md>)

### AI overview

This article describes a lightweight security-monitoring architecture for small and midsize businesses that models SaaS audit events as time series data. It explains how ordered behavior streams, baselines, dashboards, and alerts can help detect anomalies and potential breaches without deploying a full SIEM team.

### Source excerpt

When people hear that the average breach lifecycle still spans hundreds of days, they often blame inefficiency or apathy. The reality is that most teams, especially those in SMBs, are flying blind and relying on logs scattered across dozens of SaaS platforms. The information needed to understand a breach is there, but it often sits behind paywalls or is delivered without enough context to form a coherent picture. When security events are modeled as time series, they form a continuous stream of behavior rather than isolated snapshots. File downloads, admin actions, and authentication attempts shift from static snapshots to dynamic patterns. Once everything is tracked as a sequence over time, the early signs of trouble become visible far earlier than the consequences do. Digital Supply Chain Observability That realization wasn't theoretical for us. A few years ago, a third-party tool in our pipeline was compromised, and the SaaS didn't detect it--one of the SaaS's other customers did. By the time we found out, it was four months since the incident had occurred. That delay made it clear we needed to detect anomalies ourselves, without a full SIEM team or a seven-figure budget. While that incident wasn't the sole reason why we did what we did next, it was a catalyst to take security observability into our own hands. We started building an internal monitoring architecture we call DiSCO: Digital Supply Chain Observability. It's a lightweight, time series-driven system that ingests audit logs from key SaaS platforms we rely on and turns them into an ordered stream of behavior. The diagram below demonstrates the core idea: small collectors on the left, data collection via Telegraf in the middle, a time series database at the center, and dashboards and alerting tools on the right. DIY time series security You don't need to rebuild DiSCO exactly, but you can build your own version. Here's a practical path to developing a time series security detection tool without breaking the

## Telegraf Controller 1.1: Make Fleet-Wide Config Changes with a Single Edit

DevFeed: [Telegraf Controller 1.1: Make Fleet-Wide Config Changes with a Single Edit](<https://devfeed.tech/articles/telegraf-controller-1-1-make-fleet-wide-config-changes-with-a-single-edit-56908.md>)

Original publisher: [Read original article](<https://www.influxdata.com/blog/telegraf-controller-1-1/>)

Author: Scott Anderson (InfluxData)

Published: 2026-08-25T00:25:00Z

Content type: release

Language: en

Sources: [InfluxData](<https://devfeed.tech/sources/influxdata.md>)

Topics: [configuration](<https://devfeed.tech/topics/configuration.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Availability](<https://devfeed.tech/topics/availability.md>), [versioning](<https://devfeed.tech/topics/versioning.md>), [audit trail](<https://devfeed.tech/topics/audit-trail.md>)

Tags: [audit-trail](<https://devfeed.tech/tags/audit-trail.md>), [availability](<https://devfeed.tech/tags/availability.md>), [changes](<https://devfeed.tech/tags/changes.md>), [config](<https://devfeed.tech/tags/config.md>), [control-plane](<https://devfeed.tech/tags/control-plane.md>), [developer](<https://devfeed.tech/tags/developer.md>), [fleet](<https://devfeed.tech/tags/fleet.md>), [high-availability](<https://devfeed.tech/tags/high-availability.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [product](<https://devfeed.tech/tags/product.md>)

### AI overview

Telegraf Controller 1.1 introduces fleet-wide configuration management through global constants, configuration groups, aliases, and versioning. The release also adds high availability with automatic failover for Telegraf Enterprise deployments.

### Source excerpt

Telegraf is easy to stand up. You just need a config file with a few plugins and data flows. That ease is why Telegraf fleets grow fast, and why managing the agents that collect data becomes more difficult than collecting it. A change that takes minutes on ten agents takes days across a few hundred. Telegraf Controller is a centralized control plane for managing, configuring, and monitoring your fleet of Telegraf agents. Telegraf Controller 1.1 is available today and addresses that management problem from two sides: keeping the Controller layer itself reliable, and making fleet-wide changes without touching every config. The release adds high availability, configuration versioning, global constants, configuration groups, and aliases. High availability (Telegraf Enterprise) High availability lets you run multiple Controller instances from a shared database with automatic failover. If an instance goes down, agents keep pulling configuration and reporting health through the remaining instances. For production monitoring, compliance systems, and other mission-critical pipelines, the configuration layer needs to meet the same reliability requirements as the rest of the stack. High availability also simplifies planned maintenance: one instance can go offline for patching and the config path stays open. In strict environments that require redundancy, it also removes Controller as a single point of failure. Configuration versioning Configuration versioning saves every configuration change as a new version, including who made it. If an edit causes errors, compare the current version against the previous one in a side-by-side, color-coded diff and revert. Configuration history also provides an audit trail. Teams can trace when individual settings changed and test tuning changes without losing the last working configuration. Global constants Global constants let you define a value once (an output endpoint, a collection interval, a region name) and reference it from any configu

## A Guide to Downsampling Time Series Data with InfluxDB 3

DevFeed: [A Guide to Downsampling Time Series Data with InfluxDB 3](<https://devfeed.tech/articles/a-guide-to-downsampling-time-series-data-with-influxdb-3-56897.md>)

Original publisher: [Read original article](<https://www.influxdata.com/blog/downsampling-guide-influxdb-3/>)

Author: Charles Mahler (InfluxData)

Published: 2026-08-19T08:00:00Z

Content type: tutorial

Language: en

Sources: [InfluxData](<https://devfeed.tech/sources/influxdata.md>)

Topics: [Temporal data](<https://devfeed.tech/topics/temporal-data.md>), [Tutorial](<https://devfeed.tech/topics/tutorial.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [SQL](<https://devfeed.tech/topics/sql.md>), [dashboards](<https://devfeed.tech/topics/dashboards.md>), [Python](<https://devfeed.tech/topics/python.md>), [simulator](<https://devfeed.tech/topics/simulator.md>)

Tags: [aggregate](<https://devfeed.tech/tags/aggregate.md>), [dashboards](<https://devfeed.tech/tags/dashboards.md>), [data](<https://devfeed.tech/tags/data.md>), [developer](<https://devfeed.tech/tags/developer.md>), [guide](<https://devfeed.tech/tags/guide.md>), [python](<https://devfeed.tech/tags/python.md>), [sql](<https://devfeed.tech/tags/sql.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>), [time-series-data](<https://devfeed.tech/tags/time-series-data.md>), [tutorial](<https://devfeed.tech/tags/tutorial.md>)

### AI overview

This tutorial explains how to downsample high-frequency time-series data in InfluxDB 3. It compares query-time SQL aggregation with scheduled materialization through the Python Processing Engine, using a bird-tracking simulator to generate telemetry and validate 10-second aggregates.

### Source excerpt

This tutorial demonstrates both approaches using the InfluxDB 3 Processing Engine's built-in bird tracking simulator plugin. You will generate telemetry, aggregate it into 10-second windows, and validate the result with SQL. The same pattern works for infrastructure metrics, industrial sensors, application telemetry, and other time series workloads. Why downsample time series data? High-resolution data is valuable while diagnosing a recent event, but its value often changes as it ages. A temperature reading collected every second may be useful for an active incident, while a daily report may only need 10-minute or hourly averages. Downsampling helps you: scan fewer rows in long-range queries make dashboards over weeks or months more responsive retain useful historical trends at a lower resolution, reducing storage costs calculate common summaries once instead of repeating the work keep raw data only for as long as its full resolution is useful Downsampling is not the same as deleting raw data; it creates a summarized view or table at a lower granularity. Retention is a separate decision and process where data is fully deleted after a set period of time. Choose Query-Time or Persisted Downsampling InfluxDB 3 gives you two practical patterns for downsampling: Approach How it works Best for Main tradeoff Query-time SQL Uses DATE_BIN and aggregate functions in a SELECT query Exploration, flexible dashboards, and changing aggregation requirements Recomputes the result each time and does not reduce stored raw data Python Processing Engine Runs the official downsampler plugin on a schedule and writes aggregate rows to a target table Repeated long-range queries, predictable rollups, and tiered retention Requires you to choose aggregates and scheduling behavior in advance A useful starting point is to develop and validate an aggregate in SQL. If the same query becomes a frequent or expensive workload, then use the downsampler plugin. Prerequisites To follow this tutorial, yo

## A Rust Client for InfluxDB 3

DevFeed: [A Rust Client for InfluxDB 3](<https://devfeed.tech/articles/a-rust-client-for-influxdb-3-56904.md>)

Original publisher: [Read original article](<https://www.influxdata.com/blog/rust-client-influxdb-3/>)

Author: Ian Clark (InfluxData)

Published: 2026-08-13T08:00:00Z

Content type: release

Language: en

Sources: [InfluxData](<https://devfeed.tech/sources/influxdata.md>)

Topics: [Rust](<https://devfeed.tech/topics/rust.md>), [Time Series](<https://devfeed.tech/topics/time-series.md>), [API](<https://devfeed.tech/topics/api.md>), [apache-arrow](<https://devfeed.tech/topics/apache-arrow.md>), [async](<https://devfeed.tech/topics/async.md>), [Embedded Systems](<https://devfeed.tech/topics/embedded-systems.md>), [real-time](<https://devfeed.tech/topics/real-time.md>), [Software](<https://devfeed.tech/topics/software.md>), [SQL](<https://devfeed.tech/topics/sql.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [Modbus](<https://devfeed.tech/topics/modbus.md>)

Tags: [apache-arrow](<https://devfeed.tech/tags/apache-arrow.md>), [arrow](<https://devfeed.tech/tags/arrow.md>), [async](<https://devfeed.tech/tags/async.md>), [backend](<https://devfeed.tech/tags/backend.md>), [data](<https://devfeed.tech/tags/data.md>), [database](<https://devfeed.tech/tags/database.md>), [developer](<https://devfeed.tech/tags/developer.md>), [influxdb](<https://devfeed.tech/tags/influxdb.md>), [modbus](<https://devfeed.tech/tags/modbus.md>), [real-time](<https://devfeed.tech/tags/real-time.md>), [rust](<https://devfeed.tech/tags/rust.md>), [software](<https://devfeed.tech/tags/software.md>), [sql](<https://devfeed.tech/tags/sql.md>), [streams](<https://devfeed.tech/tags/streams.md>)

### AI overview

InfluxDB announces influxdb3-client, an async Rust client for InfluxDB 3 Core and Enterprise. The article describes its fit for edge gateways, embedded systems, and high-throughput telemetry pipelines, alongside existing Go and Python clients.

### Source excerpt

Time series data shows up wherever the physical world meets software. A satellite constellation streams altitude, power, and thermal telemetry from every spacecraft on every pass. A factory floor running on Industry 4.0 principles instruments every line, every motor, every batch. And underneath all of it sits a humbler problem that anyone who has worked in operational technology knows well: getting telemetry out of the PLCs and edge controllers that actually run the machines, off the bus, and into a database that can enable real-time asset intelligence. InfluxDB 3 is built for this class of workload. It is the latest generation of the InfluxDB time series engine, built on an open source stack: Apache Arrow for in-memory columnar data and Apache DataFusion as the query engine. In practice, that means InfluxDB 3 is a columnar, vectorized engine that speaks SQL, exchanges data over Arrow Flight, and interoperates with the broader Arrow ecosystem, rather than a closed world with its own bespoke query path. For high-cardinality telemetry (thousands of spacecraft channels, tens of thousands of sensor tags on a plant floor), that columnar foundation is what keeps both ingest and analytical queries fast. What has been missing for Influx users is a first-class Rust client. We just built one: influxdb3-client, an async Rust client for InfluxDB 3 Core and Enterprise that mirrors the feature set of the official Go and Python clients with an idiomatic Rust API. Why Rust, when Go and Python clients already exist? The honest answer is that for a lot of jobs, you shouldn't switch. If you're exploring data in a notebook, the Python client is the right tool. If you're writing a typical backend service, the Go client is mature and perfectly fast. Rust earns its place in the parts of a telemetry pipeline where the other two start to fight you. Here are some scenarios where it makes sense to switch: The edge box next to the PLC. The machine that bridges OPC UA or Modbus to your historia

## Where Historians Fall Short for Physical AI

DevFeed: [Where Historians Fall Short for Physical AI](<https://devfeed.tech/articles/where-historians-fall-short-for-physical-ai-56912.md>)

Original publisher: [Read original article](<https://www.influxdata.com/blog/where-historians-fall-short/>)

Author: Conrad Chuang (InfluxData)

Published: 2026-08-04T08:00:00Z

Content type: article

Language: en

Sources: [InfluxData](<https://devfeed.tech/sources/influxdata.md>)

Topics: [Physical AI](<https://devfeed.tech/topics/physical-ai.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [AI Models](<https://devfeed.tech/topics/ai-models.md>), [Training AI Models](<https://devfeed.tech/topics/training-ai-models.md>), [Inference](<https://devfeed.tech/topics/inference.md>), [Network Segmentation](<https://devfeed.tech/topics/network-segmentation.md>), [Security](<https://devfeed.tech/topics/security.md>), [systems](<https://devfeed.tech/topics/systems.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-models](<https://devfeed.tech/tags/ai-models.md>), [developer](<https://devfeed.tech/tags/developer.md>), [inference](<https://devfeed.tech/tags/inference.md>), [model-training](<https://devfeed.tech/tags/model-training.md>), [network-segmentation](<https://devfeed.tech/tags/network-segmentation.md>), [physical-ai](<https://devfeed.tech/tags/physical-ai.md>), [security](<https://devfeed.tech/tags/security.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>)

### AI overview

The article explains why traditional industrial data historians can be insufficient for Physical AI. It focuses on the need for detailed historical data for model training and low-latency telemetry for inference, highlighting limitations involving real-time access, signal-preserving data, IT/OT separation, and site-specific architectures.

### Source excerpt

Physical AI enables machines and industrial systems to perceive conditions, reason about them, and act in the real world. In industrial settings, as part of an industrial AI strategy, physical AI models can help organizations identify risks earlier, optimize operations, and respond to changing conditions in real-time. Delivering these outcomes starts with training AI models on detailed historical operational data. Then, when deployed, these models need access to real-time telemetry to interpret current conditions, make decisions, and automate actions. For organizations built around traditional historians, supporting model training and real-time operations creates new challenges and new opportunities. Where historians fall short for Physical AI Data historians remain essential systems for industrial operations. They create a durable record of process and equipment behavior, supporting engineering analysis, troubleshooting, reporting, auditability, and, where required, regulatory compliance. But the issue is, simply put, data historians were built for, well, historical data. The data requirements of Physical AI are different. At inference time, models need immediate access to current, sufficiently detailed operational data. During development and training, they need consistent, well-labeled history drawn from many operating conditions, assets, and sites. Historian-centered architectures can make both jobs difficult. Retaining Operational History Versus a Live Model Feed Data historians are effective at recording operations and helping engineers investigate what happened. But many historian deployments were not designed to continuously serve high-frequency OT data to AI models and applications operating across edge, IT, and cloud environments. The data may be collected in real-time, yet still be difficult to use in real time. Historian data commonly remains inside the OT environment, where access is constrained by network segmentation, security requirements, proprietar

## What's New in InfluxDB 3.11: A Significant Performance Upgrade for Complex Time Series Workloads

DevFeed: [What's New in InfluxDB 3.11: A Significant Performance Upgrade for Complex Time Series Workloads](<https://devfeed.tech/articles/what-s-new-in-influxdb-3-11-a-significant-performance-upgrade-for-complex-time-series-workloads-56901.md>)

Original publisher: [Read original article](<https://www.influxdata.com/blog/influxdb-3-11/>)

Author: Peter Barnett (InfluxData)

Published: 2026-07-30T07:30:00Z

Content type: release

Language: en

Sources: [InfluxData](<https://devfeed.tech/sources/influxdata.md>)

Topics: [Time Series](<https://devfeed.tech/topics/time-series.md>), [releases](<https://devfeed.tech/topics/releases.md>), [Data Management](<https://devfeed.tech/topics/data-management.md>), [observability](<https://devfeed.tech/topics/observability.md>)

Tags: [backup](<https://devfeed.tech/tags/backup.md>), [developer](<https://devfeed.tech/tags/developer.md>), [import](<https://devfeed.tech/tags/import.md>), [influxdb](<https://devfeed.tech/tags/influxdb.md>), [news](<https://devfeed.tech/tags/news.md>), [performance](<https://devfeed.tech/tags/performance.md>), [product](<https://devfeed.tech/tags/product.md>), [recovery](<https://devfeed.tech/tags/recovery.md>), [releases](<https://devfeed.tech/tags/releases.md>), [schemas](<https://devfeed.tech/tags/schemas.md>), [time-series](<https://devfeed.tech/tags/time-series.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>)

### AI overview

InfluxDB 3.11 is presented as a release for increasingly complex time series workloads. It adds faster selective queries, support for wide and ultra-sparse schemas, and a more predictable resource profile under load. The Enterprise edition also adds backup and restore, bulk Parquet import, row-level deletes, and a built-in Explorer UI.

### Source excerpt

Time series workloads rarely stay predictable for long. A system might begin with a few devices reporting a small set of measurements. As the fleet grows, new sensors come online, tags multiply, and query patterns change. A table that looked simple at the start becomes wide and sparse. A workload built around recent data expands into long-range analysis. As complexity grows, maintaining fast query performance and a predictable resource profile becomes much harder. InfluxDB 3.11 was built for that reality. Our last two releases gave users an early look at a set of performance improvements designed for heavier, more complex time series workloads. Today's release of InfluxDB 3.11 makes those performance improvements GA in InfluxDB 3 Enterprise, bringing significantly faster queries on live data, greater flexibility for wide and ultra-sparse schemas, and more predictable performance under heavy load. The release also adds new Enterprise capabilities for backup and recovery, bulk data import, row-level deletes, and cluster operations. Performance and flexibility for heavier, more complex workloads Faster Reads for Single-Series Workloads Time series applications rely on fast access to recent data, whether it's the latest reading from a device, the current state of an asset, a narrow time range from a sensor, or a live view that tracks ingest. For highly selective queries, like those for a single time series, this new release of InfluxDB 3 Enterprise is up to 4x faster than previous versions. Actual performance will vary by workload, schema, hardware, and query shape. But for industrial monitoring, fleet management, observability, energy systems, and other applications built around live operational data, these gains mean faster access to the current state of the system. More Room for Wide, Sparse, and Changing Schemas Time series data rarely arrives in one clean shape. As devices, sensors, tags, and operating environments change, schemas can become wide, sparse, and highl

## AI-Powered Spacecraft Operations with InfluxDB 3

DevFeed: [AI-Powered Spacecraft Operations with InfluxDB 3](<https://devfeed.tech/articles/ai-powered-spacecraft-operations-with-influxdb-3-56895.md>)

Original publisher: [Read original article](<https://www.influxdata.com/blog/ai-powered-spacecraft-ops/>)

Author: Charles Mahler (InfluxData)

Published: 2026-07-29T08:00:00Z

Content type: article

Language: en

Sources: [InfluxData](<https://devfeed.tech/sources/influxdata.md>)

Topics: [Demo](<https://devfeed.tech/topics/demo.md>), [Database](<https://devfeed.tech/topics/database.md>), [data](<https://devfeed.tech/topics/data.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [Model Context Protocol](<https://devfeed.tech/topics/model-context-protocol.md>), [real-time](<https://devfeed.tech/topics/real-time.md>), [Time Series](<https://devfeed.tech/topics/time-series.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [processing](<https://devfeed.tech/topics/processing.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [App](<https://devfeed.tech/topics/app.md>), [systems](<https://devfeed.tech/topics/systems.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [anomaly-detection](<https://devfeed.tech/tags/anomaly-detection.md>), [charts](<https://devfeed.tech/tags/charts.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [data](<https://devfeed.tech/tags/data.md>), [demo](<https://devfeed.tech/tags/demo.md>), [developer](<https://devfeed.tech/tags/developer.md>), [influxdb](<https://devfeed.tech/tags/influxdb.md>), [production](<https://devfeed.tech/tags/production.md>), [sensor](<https://devfeed.tech/tags/sensor.md>), [stream](<https://devfeed.tech/tags/stream.md>)

### AI overview

This article presents an InfluxDB 3 demo for monitoring a simulated fleet of 12 satellites in real time. It describes telemetry ingestion, anomaly detection during data writes, enrichment with NOAA data, dashboards for fleet and spacecraft health, and an AI agent using the InfluxDB 3 MCP server to investigate operational data.

### Source excerpt

When a satellite is drifting toward a fault, operators don't need another dashboard full of disconnected charts. They need to know what changed, what it means, and what to check before the next ground pass closes. That's the idea behind our satellite telemetry demo: a live mission-control experience built on InfluxDB 3. The demo monitors a simulated fleet of 12 satellites, continuously ingesting telemetry such as onboard computer temperature, battery voltage, solar current, reaction wheel RPM, power draw, RF link margin, ground station, orbit pass, and attitude status. One satellite is actively degrading, while historical incidents provide useful context for comparison. You can check out the live demo here or watch the video to see it in action: Demo overview From Telemetry Stream to Operator Signal The main dashboard provides a fleet overview showing which satellites are online, which are currently in contact, and where anomalies are occurring. Operators can then drill into individual spacecraft to get a more specific view and look at historical data. Detecting Anomalies as Data Arrives Behind the scenes, the InfluxDB 3 Processing Engine observes incoming data as it is written to the database and automatically creates alerts based on conditional thresholds or sensor states. That means anomaly detection happens without waiting for a separate pipeline to catch up. Another processing engine task incorporates NOAA data for environmental context alongside vehicle behavior. This pattern can be extended beyond satellites. Any connected system with high-volume and time-sensitive data, such as industrial equipment, energy infrastructure, production systems, or logistics networks, will benefit. Accessing Operational Truth Using AI This demo also includes an AI agent powered by the InfluxDB 3 MCP server. Instead of generating answers based on generic knowledge, the agent can access data stored in InfluxDB. You can ask about fleet health, a specific satellite, or the root caus

## What's New in InfluxDB 3: 5 New Processing Engine Plugins

DevFeed: [What's New in InfluxDB 3: 5 New Processing Engine Plugins](<https://devfeed.tech/articles/what-s-new-in-influxdb-3-5-new-processing-engine-plugins-56894.md>)

Original publisher: [Read original article](<https://www.influxdata.com/blog/5-new-processing-engine-plugins/>)

Author: Charles Mahler (InfluxData)

Published: 2026-07-23T08:00:00Z

Content type: release

Language: en

Sources: [InfluxData](<https://devfeed.tech/sources/influxdata.md>)

Topics: [processing](<https://devfeed.tech/topics/processing.md>), [Inference](<https://devfeed.tech/topics/inference.md>), [model-deployment](<https://devfeed.tech/topics/model-deployment.md>), [Python](<https://devfeed.tech/topics/python.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [JSON Schema](<https://devfeed.tech/topics/json-schema.md>), [Database](<https://devfeed.tech/topics/database.md>), [Command-line interface](<https://devfeed.tech/topics/cli.md>)

Tags: [aws](<https://devfeed.tech/tags/aws.md>), [developer](<https://devfeed.tech/tags/developer.md>), [hugging-face](<https://devfeed.tech/tags/hugging-face.md>), [inference](<https://devfeed.tech/tags/inference.md>), [influxdb](<https://devfeed.tech/tags/influxdb.md>), [json-schema](<https://devfeed.tech/tags/json-schema.md>), [processing](<https://devfeed.tech/tags/processing.md>), [python](<https://devfeed.tech/tags/python.md>), [tensorflow](<https://devfeed.tech/tags/tensorflow.md>)

### AI overview

InfluxDB introduces five Processing Engine plugins, including integrations for SageMaker inference, value counting, Chronos forecasting, data replication, and stock portfolio tracking. The plugins run inside InfluxDB 3's embedded Python runtime and can be triggered by schedules, data writes, or HTTP requests.

### Source excerpt

The InfluxDB team has released five new Processing Engine plugins. They range from making it easy to call a hosted ML model to pulling in stock market data in real-time. Every one of them can be activated with a few terminal commands. No external services or tools--they all run inside your existing InfluxDB instance. Here's what's new, when you'd reach for them, and a few quickstart examples to get you going in minutes. Processing Engine primer If you aren't familiar, the Processing Engine is an embedded Python runtime inside InfluxDB 3 that allows you to execute Python code on the following triggers: Schedule - Run code at scheduled intervals Data write - Runs whenever data is written to a table Request - A custom HTTP endpoint that handles incoming requests Plugins can query InfluxDB, transform your data, and write it back to a new table. They can also be used to hit external services outside InfluxDB. SageMaker inference The SageMaker plugin pulls rows of data, formats them how your SageMaker model expects, calls the model endpoint, and writes the prediction back to InfluxDB. It can build CSVs or 8 different JSON schema options, so it supports TensorFlow Serving, AWS' built-in algorithms, and Hugging Face models. This plugin allows you to use your deployed SageMaker models without having to create a custom plugin. Just point the plugin at your endpoint to get anomaly scores, classifications, forecasts, or whatever else your endpoint returns, and have it written directly to InfluxDB. Example: Anomaly Scoring with Built-In AWS Model influxdb3 install package boto3 influxdb3 install package pandas influxdb3 create trigger \ --database iot \ --path "sagemaker.py" \ --trigger-spec "every:30s" \ --trigger-arguments 'endpoint_name=rcf-anomaly,source_measurement=metrics,feature_order={cpu}|{mem}|{rps}|{p99_ms},json_shape=instances_features,output_fields=anomaly_score=scores[*].score,interval=2min,limit=20' \ rcf_score With this setup, every 30 seconds the last 20 rows of

## Inside LeoLabs: How Radar Engineers Track Over 27,000 Objects in Orbit with InfluxDB

DevFeed: [Inside LeoLabs: How Radar Engineers Track Over 27,000 Objects in Orbit with InfluxDB](<https://devfeed.tech/articles/inside-leolabs-how-radar-engineers-track-over-27-000-objects-in-orbit-with-influxdb-56903.md>)

Original publisher: [Read original article](<https://www.influxdata.com/blog/inside-leo-labs-influxdb/>)

Author: Cole Bowden (InfluxData)

Published: 2026-07-21T08:00:00Z

Content type: article

Language: en

Sources: [InfluxData](<https://devfeed.tech/sources/influxdata.md>)

Topics: [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Database](<https://devfeed.tech/topics/database.md>), [real-time](<https://devfeed.tech/topics/real-time.md>), [Time Series](<https://devfeed.tech/topics/time-series.md>), [data](<https://devfeed.tech/topics/data.md>), [Network](<https://devfeed.tech/topics/network.md>), [Software](<https://devfeed.tech/topics/software.md>)

Tags: [data](<https://devfeed.tech/tags/data.md>), [influxdb](<https://devfeed.tech/tags/influxdb.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [network](<https://devfeed.tech/tags/network.md>), [radar](<https://devfeed.tech/tags/radar.md>), [software](<https://devfeed.tech/tags/software.md>), [software-engineer](<https://devfeed.tech/tags/software-engineer.md>), [space-technology](<https://devfeed.tech/tags/space-technology.md>), [use-cases](<https://devfeed.tech/tags/use-cases.md>)

### AI overview

An article about how LeoLabs uses InfluxDB to manage real-time radar data for tracking satellites and debris in low Earth orbit. The system supports continuous monitoring, collision avoidance, and satellite operations while reducing the database-management burden on engineers.

### Source excerpt

Every month, satellite operators perform thousands of orbital maneuvers as recommended by LeoLabs' data. They don't do it to reposition satellites, they do it to avoid hitting things. With tens of thousands of active satellites and other debris circling the Earth, adding new devices to orbit comes with risk. Satellites are expensive, high-tech devices that require a massive investment to engineer and launch. This means that to get a return on that investment, companies need their satellites to last a long time and to avoid the hazards posed by other satellites and debris in similar orbits. Space is big, but it's becoming increasingly crowded as investment in the commercial space sector skyrockets. A satellite in low Earth orbit is unlikely to bump into something else on any given day, but when the expectation is that its lifespan will be on the scale of 5 to 10+ years--thousands of days--that small chance of collision becomes a greater risk. Collisions can take a satellite out, and without the necessary intelligence to avoid other objects around it, there's no guarantee a satellite can last its full lifespan. We sat down with Jackson Ball, a radar software engineer at LeoLabs, to talk about what his company is doing to monitor satellites and discuss how it's using InfluxDB to track and leverage radar data. Armed with a massive stream of real-time data, LeoLabs enables satellite operations by handling the around-the-clock task of managing, monitoring, and positioning objects in orbit, ensuring that its customers don't have to worry about the 10+ fragmentations a year that happen in space. What is LeoLabs? LeoLabs is a Silicon Valley-based space technology company that operates a global network of ground-based radars across the United States, Europe, Australia, and other regions. Its systems are designed to detect, track, and characterize satellites and debris in low Earth orbit, contributing to space traffic management, space domain awareness, and collision avoidance.

[Next page](<https://devfeed.tech/sources/influxdata.md?cursor=WyIyMDI2LTA3LTIxVDA4OjAwOjAwKzAwOjAwIiwgImMxYjJmNWMyLTNhMjQtNGZhMi05NmNiLWFmZDZiYThiZjI4ZiJd>)