Operations | Monitoring | ITSM | DevOps | Cloud

This blog post is part of PagerDuty’s ongoing series on how we’re helping customers navigate their journey towards autonomous operations. Read on to learn about how Custom Field Mapping for PagerDuty’s plugin for both Spotify for Backstage and Spotify Portal for Backstage now generally available builds towards this vision. It’s 2am. A Sev-1 fires, and your on-call responder opens the incident in PagerDuty. What’s waiting for them? A service name, and not much else. No tier.

This blog post is part of PagerDuty’s ongoing series on how we’re helping customers navigate their journey towards autonomous operations. Read on to learn about how recent SRE Agent Enhancements build towards this vision. During an incident, everything is competing for attention at once. Responders lose time swiveling between tools, insights gathered by AI stay siloed instead of feeding into the next decision, and the pressure to move fast means learnings rarely stick.

This blog post is part of PagerDuty’s ongoing series on how we’re helping customers navigate their journey towards autonomous operations. Read on to learn about how Event Enrichment builds towards this vision. Every on-call engineer knows the drill. An alert fires. It tells you something is wrong, but not what it means. Is this asset in maintenance? Which team owns it? Is it customer-facing?

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.

Warehouse workers don’t think about whether their mobile interface runs on a browser. They’re focused on getting the job done. But for operations and IT teams evaluating or upgrading mobile technology in supply chain environments, platform choice matters more than most people realize. Consumer mobile browsers such as Safari, Edge and Chrome are useful tools designed for everyday web use. They help people search, shop, read, collaborate and access web applications from almost anywhere.

OrionIQ’s agentic investigation is now built into Logz.io Open 360 AI. Ask a question and OrionIQ investigates across your telemetry, shows its work as it goes, links every finding back to the exact query behind it, and tells you how much to trust the answer. Today we’re bringing OrionIQ Chat into Open 360 AI. This is the first OrionIQ product to ship inside the Logz.io platform, and it’s the same agent that powers the standalone OrionIQ app, now available right where you already work.

To measure AI ROI, compare attributable value (revenue lift, cost savings, engineering time recovered, risk reduction) against fully loaded AI spend (API usage, subscriptions, infrastructure, people time) at the unit level: per initiative, per team, per task. The formula is simple. The instrumentation is the hard part, and it's where most organizations are failing: in CloudZero's 2026 survey, 34% of finance leaders couldn't produce a credible ROI number at all.

You’re probably already tracking the metrics that matter most in your Analytics dashboards like unit economics, AI ROI, and spend by team. Now you can put a target on any of them. Pick the metric, set the threshold, and CloudZero emails you when it’s crossed, with no ticket to us, no custom build.

Updated August 05, 2026 Keyword monitoring checks that a specific string is still present in a page or API response on every run, instead of trusting the HTTP status code. It catches the failures that uptime checks sleep through: a deploy that renders an empty template, a CMS entry someone unpublished, a checkout page serving "Something went wrong" with a perfectly healthy 200. In Hyperping, the simple version is a text body assertion on an HTTP monitor and takes about ten seconds to set up.

Recently, I’ve been playing around with the ansible promise type by Fabio Tranchitella. It’s amazing how easy it is to leverage the benefits of agents with all the existing automation from the ansible community. Hence, I wanted to share it in a blog post, with an emphasis on easy. Let’s start off by creating a new cfbs project in a cfengine-ansible directory. Make sure to answer yes on the prompt to build on top of the default policy set.