Operations | Monitoring | ITSM | DevOps | Cloud

Grafana 13.2 is here, bringing more improvements to help you and your team explore your data and get to insights faster. Download Grafana 13.2 In this post, we’ll highlight the latest updates to saved queries, a feature that lets teams share, discover, and reuse queries to get to trusted answers faster and help new teammates get up to speed. We’ll also explore how the new View panel sidebar makes exploring busy panels a breeze.

Vulnerabilities used to move at human speed. A researcher found one, disclosed it, and defenders had days - sometimes weeks - to respond before it was weaponized in the wild. That window is gone. According to the Edgescan 2026 Vulnerability Statistics Report, it still takes an average of 55 days to fix a vulnerability - but the Zero Day Clock shows attackers going from disclosure to first exploit in as little as 6 hours.

Splitting one big pull request into five smaller ones doesn’t automatically make review faster. It just moves the complexity from the diff to your head, unless something keeps track of the order for you.

Effective incident response depends on having all of the context surrounding what’s happening. You have to understand your systems, services, architecture, and teams deeply enough to correctly interpret whatever alert just fired. Too often, that context doesn’t arrive packaged neatly in one place. Gathering and interpreting context correctly under time pressure is one of the most difficult parts of the job.

Here's a scenario that will likely sound familiar: You’re building an executive overview dashboard that you would put on a wall-mounted screen so the whole room can see how the business is doing at a glance. It’s for a Shopify online store, and displays a mix of business and application signals, including latency panels, error-rate panels, and a big stat panel for revenue-per-week. It looked great. But something is missing.

GitKraken Desktop 12.4 gives developers running several worktrees and AI agent sessions a single graph to see it all, plus an inline way to approve or deny what each agent wants to do. It ships August 4, 2026, with updates carried forward from 12.1 through 12.4.

Summary InfluxDB 3.11 delivers major performance and data management updates for growing time series workloads, with significantly faster queries on recent data, expanded support for wide and ultra-sparse schemas, and a more predictable resource profile under load. InfluxDB 3 Enterprise also adds backup and restore, bulk Parquet import, row-level deletes, and a built-in Explorer UI.

Five coding agents sounds like leverage right up until a developer is the one keeping track of all five: one fixing a bug, one building a feature, one refactoring, and two waiting on input at the same time. AI did not create that problem. It exposed a workflow problem that was always going to surface once parallel development became normal instead of occasional.

Billing has always been one of the parts of running an MSP that doesn't scale on its own. More endpoints, more tickets, and more monitors under management all mean more usage to track—and for most MSPs, that usage still gets tallied by hand before an invoice can go out. Not anymore. We're rolling out the MSP Central billing module, powered by our integration with Zoho Billing—and it's live with usage-based billing from day one.

Summary The five most recent plugins from the InfluxDB team are live: Sagemaker, value counter, Chronos forecasting, simple data replicator, and a stock portfolio tracker. Table of Contents 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.