Operations | Monitoring | ITSM | DevOps | Cloud

1,238 API errors in two days, and every response said 200 OK

The query count in our snapshot drawer went blank, and the unit test for that request kept passing. When we went looking in recorded traffic, the API gateway had rejected that request 210 times in a single recording. Every one of those rejections came back as 200 OK. So we searched the rest. We record our own API gateway with Speedscale, and two recording windows from November 3 to 5 (about 38 hours between them) held 1,238 responses with gRPC status INVALID_ARGUMENT. All 1,238 returned HTTP 200.

Time to Rethink VMware Monitoring?

Recent security disclosures have put the Veeam Management Pack for Microsoft System Center under scrutiny. Security researchers have identified three remote code execution vulnerabilities, including one rated Critical (CVSS 9.3). According to Veeam’s security advisory, versions 9.1 and earlier in the 9.x product line are affected. Veeam will not provide a separate security fix for these versions.

AI cost visibility: how to see AI spend as it happens (2027)

AI cost visibility is the ability to see what AI spend is buying, by person, team, feature, customer and activity, before the bill arrives. The invoice can't provide it: it records tokens and hours, not decisions. It comes from capturing each AI event as it occurs, with business context attached, and reconciling to the bill. Take 50 million input tokens and 10 million output tokens in a month. On Claude Haiku 5.5 that is $10. On Claude Fable 5.1, the same tokens cost $1,000.

AI ROI measurement: what the 23% do differently

23% of finance leaders can both allocate AI spend systematically and prove its return to a board. Only 3% of them failed to secure an AI investment, against 19% of everyone else, and they spend what their peers spend: 41% plan a FY2027 increase of 20% or more, against 38%. Measuring return alone buys nothing, because companies claiming ROI they cannot allocate report the same board-proof gap as companies claiming no return at all.

Are your Kubernetes CPU limits actually being enforced?

CPU limits are one of the first guardrails most teams add to a Kubernetes manifest. Set resources.limits.cpu: 200m, and you can trust that the container will never use more than a fifth of a core…right? That’s not always the case. A CPU limit is a request, not a restriction: the kubelet can ignore it, and if that happens, the container is free to use as much CPU time as it wants.

Tracing with OpenTelemetry on OpenSearch

TL;DR This post is for architects who want to add tracing to Aiven for OpenSearch and need to know what it takes to run the pipeline. Aiven for OpenSearch includes Trace Analytics in OpenSearch Dashboards, so you can follow a request across services, see which services call which, and open the logs a slow span wrote. OpenTelemetry collects the traces, and Data Prepper writes them to the span and service map indexes that Trace Analytics reads.

The missing piece: bringing up to 15 years of support to Zephyr for microcontroller-based ECUs

We recently announced the launch of Zephyr 26.04 LTS, bringing up to 15 years of security maintenance per LTS and enterprise lifecycle management to microcontroller-grade devices. While central high-performance computer ECUs capture most of the industry spotlight in software-defined vehicle (SDV) architectures, the operational reality of modern vehicles is far more distributed.