Operations | Monitoring | ITSM | DevOps | Cloud

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.

Your Playwright test clicks Next page, waits for the item list, and times out. Now you’re digging through a trace to find out whether the page broke or an API call failed. Traditional browser-testing workflows focus on clicks, page state and UI assertions. Those checks tell you whether a user journey works, but investigating a failure also means understanding the APIs behind the page.

Change one field in a.proto from double to string, and nothing complains. The code compiles, the deploy goes green, and a service still built from the old contract keeps answering with a double. Here’s what Go’s protobuf runtime does when a client on the new contract reads that answer: No error. risk_score comes back empty, and the nine bytes of the double are tucked away as unknown fields.

Replay a GraphQL recording at the server that produced it, and every request comes back 200 OK. Here is one of those 200s, from a Session query whose recorded token has expired: A GraphQL server reports most failures inside a successful HTTP response, so any check that stops at the status code passes this request. And that is the second way GraphQL hides from URL-shaped tooling.

A readiness check should make a release safer. During one release validation, ours kept Kraken’s traffic replays stuck in Initializing until they timed out. The operator was asking Kubernetes for EndpointSlices. Its installed permissions did not allow that request. The code needed a real cluster, the generated permissions, and a replay trying to start before that mistake became obvious. Kraken put those pieces together during release validation.