Operations | Monitoring | ITSM | DevOps | Cloud

When SAP unveiled the Business AI Platform at Sapphire 2026, it folded BTP, Business Data Cloud, and Business AI into a single governed environment. BTP didn’t disappear but became essential architecture underneath SAP’s agentic AI direction. A big part of the repositioning included cloud and AI enablement of existing systems, data and enterprise context: the cloud half of every hybrid SAP estate just got more capable and more strategic, and SAP Cloud Connector plays a central role.

A system refresh in SAP is the process of copying data, most often from Production, into a QA or test system so that testing happens against realistic, current data. Manually, it’s one of the most time-consuming recurring tasks a Basis team owns.

An SAP system is an installed instance of SAP’s business software that runs an organization’s core processes, like finance, supply chain, and HR, on a single, shared database. If you’re new to a company that runs on SAP, this guide explains what that actually means: what the software does, what an SAP system is made of, and why companies talk about DEV, QAS, and PRD like they’re three different things. They are.

On-call burnout is no longer a fringe complaint. It is one of the loudest signals in the 2026 reliability data. A wave of fresh industry research this year points to the same uncomfortable conclusion: the people who keep systems running are running on empty. In the DuploCloud 2026 AI and DevOps Report, 47 percent of engineers said DevOps overload contributes to burnout, with on-call rotations and repetitive maintenance singled out as primary culprits.

Impossible travel and new-country sign-in alerts are famously noisy. The reasons why, the difference between the Entra ID and SharePoint signals, and what separates a real account takeover from proxy egress.

When a Terraform run feels slow, most teams are flying blind. The run log in HCP Terraform tells you what happened, but not what took so long—and it certainly doesn't roll up across hundreds of runs so you can spot a trend.

Software supply chain engineering has reached a critical inflection point. As autonomous AI coding agents transition from generating autocomplete suggestions to planning, writing, reviewing, and deploying entire software pipelines without humans in the loop, the connection between human intent and production binaries is fracturing.

The hidden cost of multicloud lives in operations and governance. Each provider develops its own console, runbooks, and audit posture, and the gaps widen quietly. The bill comes due at the next migration, audit, or incident.

Python is the native language of AI-assisted development. Models are really good at writing it, and a lot of people are now shipping it without ever having written much Python themselves. The whole thing is really simple. You prompt an app, Claude Code or Cursor produces a working Flask or FastAPI backend, and you’re live in a few hours. However, there’s still a big difference between “it works on my machine” and “it works in production”.

In July’s episode of This Month in Datadog, Ruxanda Lueck joins Jeremy for a conversation about how you can confidently evaluate and release features that contain AI-generated code. She also discusses her career trajectory from containers to AI, how agentic workflows impact trust during feature development, and the challenges of testing nondeterministic agent behavior.