Operations | Monitoring | ITSM | DevOps | Cloud

Somewhere in your service is a branch that has never executed. Not a rare one, a never one. It handles a dependency being unavailable: it reads from a cache, it returns a stale value, it marks the response degraded so callers know not to trust it too far. It was written carefully. It was reviewed. Whether it works is an open question, because nothing in the test suite makes that dependency fail, and the dependency does not fail on request.

Scoped chaos rules are now in proxymock. A filter query picks the traffic, an effect perturbs it, and every response that gets touched is labelled so you can tell an injected failure from a real one for the rest of the run. Available in v2.5.892 and newer. The short version of why: kill a pod and you learn something real, but you do not learn what your service does when a dependency stays up and starts lying to it.

If you've ever inherited a cluster that nobody fully understands, or watched two teams solve the same infrastructure problem in completely different ways, you've already felt the cost of not having a template strategy. It's not always dramatic; it starts with a different CNI here, a missing cert-manager version there, but it compounds. Six months later, cluster configuration is tribal knowledge, and the platform team has become the bottleneck.

Testing consumes up to 50% of CI/CD pipeline time. That’s the single most expensive place in your delivery pipeline, and a meaningful share of that time is often wasted running tests unaffected by the change. Every time a developer pushes a commit, the full test suite runs. A two-line bug fix in auth.py triggers 2,000 tests, including 1,900 that don’t touch anything near auth.py. Those unrelated tests are overwhelmingly likely to pass, but the pipeline still spends 20 minutes running them.

Over the past year, federal agencies gained broad access to enterprise AI through the OneGov initiative, at prices unlike any normal software deal. The current OneGov portal lists OpenAI ChatGPT Enterprise at $1 per agency, Anthropic Claude at $1 per seat, and Google Gemini for Government at $0.47 per agency. Those introductory offers begin expiring on September 30, 2026, the final day of fiscal year (FY) 26, which places renewal squarely in the FY27 planning cycle.

At Datadog, we want to expose our engineers to high-quality AI tools and workflows. However, token usage can be expensive, and finding a balance between AI cloud spend and the return on investment can be difficult. But what if engineers could maintain their current AI workflows using the same tools, but at a lower cost?

In conversations with customers, compliance rarely starts as a tooling discussion. It usually starts with a practical concern: how do we keep moving, keep modernizing, and still know that our infrastructure is aligned to the policies we are accountable for? That question comes up because the pressure is real. Teams are managing hybrid estates, responding to audit requests, dealing with drift, supporting new platforms, and being asked to move faster without creating more risk.

New pricing for Aiven for Apache Kafka is now live for all new customers on AWS, GCP and Azure. For our existing customers: nothing changes. When choosing your cluster you are guided by three things: And you pay for three things.

CUR 2.0 is generally available and on by default, so every AWS connection you make now starts with the richest billing data AWS offers. That richness is important. CUR 2.0 carries AWS caller identity, which is what puts Bedrock and other AI spend on the role that drove it instead of leaving it as one number in your bill. It also populates AWS Account Name automatically. Both of those are yours the moment the connection is live. Getting there is a single step now.

GitHub Copilot Enterprise pricing is $39 per user per month, and since June 1, 2026, each seat includes $39 in monthly GitHub AI Credits, pooled across your whole organization and consumed by token usage at per-model rates. The seat price is fixed. The bill is not: usage beyond the pooled credits is charged on top, which is why the real Enterprise question in 2026 isn't the price per seat. It's your engineers' token consumption.