Operations | Monitoring | ITSM | DevOps | Cloud

The latest News and Information on APIs, Mobile, AI, Machine Learning, IoT, Open Source and more!

Shipped: Slice AI spend eight ways in AI Explorer

You can already break down cloud spend by team, product, or customer in Explorer. But AI spend has been harder to decompose. Which models is each team running? What activity is driving the cost growth you saw this month? Before AI Explorer, answering those questions meant exporting raw event data and building your own breakdowns, or waiting days for reconciled billing to land in Explorer.

Adding friction to your AI spend isn't saving money. It's costing you growth.

Enterprises are putting hard ceilings on AI spend. Accenture now centrally funds $29 a month per person for Claude and charges anything above that to a project budget code. Uber used up its 2026 AI budget in four months and restricted access. A cap stops waste and useful work at the same rate. The alternative is seeing AI cost by team, by project and by outcome, then funding what returns. Companies spent the past year telling employees to use more AI. Now a lot of them are putting a lid on it.

Test AI-Generated Code with Real Traffic#aiagents #devops #observability #shiftleft #softwaretesting

AI can generate code in seconds, but testing it against real production behavior is where developers get stuck. Learn how capturing and replaying actual production traffic in development helps you catch bugs before you deploy!

What's New in Scout: October 2026

October was about making Scout’s data easier for AI tools to use and easier for your team to trust. Scout is now in Claude’s connector directory, the MCP server got leaner and more careful about what it returns, and Scout Trails opened its beta. Anomaly Detection also became easier to read and better at catching short spikes. Here’s what shipped in October.

AI Visibility Checkers for Engineering-Led Teams: 7 Best in 2026

Somewhere in your edge configuration there is a rule nobody remembers writing, and it is deciding whether ChatGPT can read your documentation. That is the thesis of this list: AI visibility, meaning whether assistants such as ChatGPT, Gemini and Perplexity name your product when a buyer asks for one, has become partly an infrastructure problem, and the two failure modes that matter most sit on the engineering side of the house. The first is reachability, because a WAF default that returns 403 to GPTBot or ClaudeBot removes you from retrieval as surely as a robots.txt disallow.

Policy as code for AI coding: How to turn engineering standards into guardrails for AI agents

Key Takeaways Engineering standards exist in every organization. They cover how services communicate, how secrets are managed, who reviews changes before they merge, and what "production-ready" means. The problem is where those standards live: wiki pages, onboarding docs, the memory of whoever happens to review a pull request that day. Conventional enforcement depended on reviewer knowledge, which varied across teams.