Operations | Monitoring | ITSM | DevOps | Cloud

There's a specific, recognizable point where a team's use of AI agents changes shape. Not when they adopt agents; most teams already have. It's when agents stop running on someone's laptop and start running on infrastructure that the whole team can see. This is a real technical shift, not a policy change or a maturity score. Here's specifically what's different on each side of it.

Back in July, I wrote about how the Tenant team (the team behind Honeycomb Private Cloud (HPC)) has embraced the code review bottleneck to focus more of its work. One of the other challenges we have is that we're downstream of almost all the other teams at Honeycomb, meaning that we have to package up everyone's code and services, and how it gets provisioned! This is something impossible to handle through code review since there are so many engineers on other teams, and so few of us.

Most people who use CloudZero spend their time in one or two places. For some it’s AI Signals, and for others it’s Optimize or Anomalies. If Explorer isn’t one of those places, every sign-in starts with a click to get where you need to be. Dates and numbers are another friction. A date like 04/07 means April 7 in the US and July 4 in much of Europe. When the platform shows a format your team doesn’t use, you end up having to convert each value before you can work with it.

Pair Kinesis PartitionKey with ExplicitHashKey to propagate OpenTelemetry trace context while keeping records on their original shards and preserving order.

SharePoint and OneDrive pay-as-you-go billing (MC1330893, MC1477185) and the end of the OneDrive allowance above 5 TB (MC1465765): who is affected.

How to classify data in SharePoint Online: classifiers, labels, auto-labeling and on-demand scans, where each one stops, and how to reach archived content.

All 23 failure codes Purview reports when auto-labeling a SharePoint file fails: which retry on their own, which need action, and where to find the code.

Discover why engineers ignore cloud cost governance and how to build developer cost accountability. Learn how Harness helps empower engineering teams. Engineers often overlook cloud costs due to friction in traditional FinOps tools and a lack of real-time visibility. By embedding automated guardrails and shift-left cost insights into developer workflows, organizations can drive accountability without slowing velocity.