Operations | Monitoring | ITSM | DevOps | Cloud

AI agents can help investigate failed builds, fix flaky tests and automate other development tasks. But setting up those agents has required more Pipelines configuration than it should. Agent-powered steps often need different compute, permissions and runtime settings from ordinary build and test steps. Until now, teams have either repeated those settings across every agent-powered step or tried to make one set of global defaults work for everything.

The best API monitoring tools are Hyperping for HTTP and API checks with on-call and status pages, Checkly for API monitoring as code, Postman Monitors for teams that already keep collections in Postman, Datadog for connecting failed checks to traces and logs, Grafana Cloud for teams using k6, Better Stack for checks inside a broader incident workflow, and UptimeRobot for inexpensive availability checks.

Somewhere in every compliance program is a person who spends the week before an audit pulling logs out of several different systems, reconstructing who had access to what, and hoping the screenshots match what the auditor actually asks for. None of this work makes the system more secure. It just makes the existing security visible to someone who's checking. That gap, between the controls that are actually in place and the evidence that proves it, is where most audit prep time goes.

We’re back with another major SIGNL4 update! This release brings new features and improvements across Call Routing, User Profiles and Management, Stakeholder Communication, and AI.

How much of your database delivery can you actually see? For most teams, the picture is scattered. Deployment status lives in CI logs and scripts. Drift appears outside the process. And with AI multiplying the volume and speed of changes moving through pipelines, the risk that comes with low visibility rises with every release.

The State of Agent DLC 2026 asked 700 organizations already running AI agents how confident they were across five domains: testing, security, inventory, cost, and rollback. Confidence came back between 74% and 77% in every domain we tested. In most of them, the controls that would justify it are not there. “No, I don't have a nanny cam, but I'm sure my kids are OK.