Operations | Monitoring | ITSM | DevOps | Cloud

From the first alert to the root cause, without leaving the page. TL;DR: Investigating an incident is a series of quick questions, each one leading to the next. Until now, Explore made you stop between questions to translate them into syntax, switch modes or rebuild a chart. The new Explore lets you go straight from one question to the next: one workspace, any dataset, any team, any way you like to ask. Here’s what that looks like on a real night on call.

When an auditor tests a control, they ask two questions about each change: was the control met, and what evidence shows how that result was reached? Most automated controls can answer the first. A Rego policy returns allow: true or allow: false, but says nothing about what it checked. Engineers can hand-write violation messages to explain a failure, but a passing check leaves no record at all. When an auditor asks how a change passed, someone has to reconstruct the answer.

AI Budgets turns an AI cost policy into a limit customers can watch hold in real time, so overspend gets caught within days instead of surfacing on next month's invoice. With AI Budgets, the Cost Management Agent turns your AI cost policy from a document everyone signed once and forgot into a limit you can see working. ‍ In our last post, we showed why 73% of organizations have an AI cost policy, but only 13% can tell whether it's working.

VegaLoad is a free, open-source load testing tool for agentic developers. Your agent writes the test, runs it, and gives you a report. VegaLoad is a free, open-source load testing tool. You ask your agent for a test. It writes the file, runs it, and gives you a report.

session start tool call tool call cost outcome AI coding agents have quietly become part of most engineering teams. They open files, run commands, call tools, and push changes, often for hours at a time. Yet when you want to know what an agent actually did, the answer usually lives in one developer’s terminal history, and it disappears when that session closes.

GitLens 19.4 makes it easier to get into your repository, understand your Git history, and start working without extra setup. The biggest change is simple: the Commit Graph is now available without a GitKraken account for public and local repositories. Open GitLens, open the Graph, and start exploring. No sign-in required. For private repositories, GitLens also gives you a 3-day preview of the Commit Graph without requiring an account, so you can experience the workflow before deciding what comes next.

How often does a lagging replica or a bad network link reach users before your monitoring flags it? The problem grows when every layer has its own tool. Warning signs then show up in different places, often too late to act on. Motadata 8.2.9 came out on October 5, 2026, with eight updates to Motadata ObserveOps. Four of them focus on the network. The other four deal with databases, data streaming, alerting and SEBI compliance reporting. A few add support for technologies Motadata did not cover before.

At home I run fully automated coding loops on a few side projects. They use more than 100-million tokens a day. At Claude Opus 5.5 prices, that costs more than $5,300 a month. For hobby projects. The same usage on DeepSeek V4.1 Flash cost about $330 a month, one sixteenth of the price. If we want to keep scaling how much we use AI, most of those tokens have to run on open models, period.

Today Canonical announced the release of Ubuntu 26.10, codenamed “Stonking Stingray,” available to download and install from ubuntu.com/download. Building on previous releases, Ubuntu 26.10 advances enterprise security features, completes the rollout of the Rust-based uutils coreutils, and strengthens integrations for user authentication using Microsoft Entra ID.

AlloyScan 26.10 brings remote computer restart, more flexible dashboard Analytics, and customizable system notification emails. Take a look at what’s new.