Operations | Monitoring | ITSM | DevOps | Cloud

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

Discover Aiven for DataHub: a fully managed, open-source data catalog that gives your teams and AI agents the context they need to find and understand data. According to an MIT study, 95% of AI projects fail to deliver value. I've been thinking about why that number is so stubbornly high, and I've come to believe the answer isn't about models,compute or even data quality in the traditional sense -It's about context.

One space character, one broken backup. See how Aiven’s engineering team traced an OpenSearch k-NN bug to its source and implemented a lasting fix. Backing up your OpenSearch indexes via the Snapshot process is vital for disaster recovery, allowing you to restore the indexed data, cluster configuration and state if something goes wrong.

Unify your code and data. Aiven Apps lets teams deliver real-time applications faster, without building new platforms. No lock-in. No custom pipelines. No egress surprises. We are excited to announce the Limited Availability (LA) launch of Aiven Apps! For over a decade, Aiven has simplified how you store and stream data with an open-source foundation. Over that same time, data volumes have exploded, and so has the friction caused by the distance between where your data is stored and where your code runs.

Our Q1 momentum has been focused on a simple goal: making InfluxDB easier to operate, easier to scale, and faster to put to work. Across Telegraf, InfluxDB 3, and our managed offerings, these updates reduce friction in how teams collect, process, and scale time series workloads.

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