Operations | Monitoring | ITSM | DevOps | Cloud

speedscale

Which Bugs AI Agents Fix Better With Traffic

Jun 29, 2026 By Ken Ahrens In Speedscale
In the first experiment, I wanted a baseline: if an AI coding agent gets the same production signal a human would get, can it fix bugs in a codebase it has never seen? Yes, but only when I gave it better context. With only an alert, the agent passed 51% of the runtime tests. When I added captured traffic, the actual request and response for the failing call, it climbed to 77%. This post is the second pass.
Read Post
Sponsored Post
speedscale

Five things your logs will never tell you

Jun 22, 2026 By Matthew LeRay In Speedscale
A customer escalation hit my queue when I was on the customer smoke jumpers team at an observability vendor. My team was the group that parachutes into Fortune 500 accounts one bad week from churning and usually after a big customer outage. The customer had filed a billing dispute three weeks earlier and their on-call engineers were stuck. They had our full stack: logs, metrics, traces, end-to-end instrumentation, every product we sold and some we didn't. They could see the request came in. They could see it returned a 500. They could not see the body. The trace was sampled out. The log line was truncated at 4KB.
Read Post
speedscale

Beware of PII in Testing Data: The Security Iceberg and Where PII Actually Hides

Jun 19, 2026 By Speedscale Team In Speedscale
If you run a platform tools or security team, you have likely heard this request from developers: “I just need a copy of the production database for staging so I can run realistic load and integration tests.” It is a completely reasonable request. Production traffic and data contain the actual request shapes, real-world value distributions, long-tail anomalies, and timing patterns that make tests useful.
Read Post
speedscale

Build WireMock mappings fast from real traffic

Jun 18, 2026 By Ken Ahrens In Speedscale
I’m a big fan of service mocking. I’ve been working in and around software for about 25 years, and one thing never changes: when you sit down to work on your code, you almost never have everything available. The database, the third-party API, the message queue, the service two teams over. Something’s missing. So you’ve got to stub it out or mock it out and keep moving.
Read Post
speedscale

Capture once, test forever

Jun 12, 2026 By Ken Ahrens In Speedscale
We’ve gotten used to understanding our applications through signals, summaries, and traces. Tiny little bits of information about how the app really works. Not because that’s the best way to do it, but because it’s been too hard to get the real thing. The real information exists. It’s on the network. How people called your app and what your code did. What other systems it called, the database queries it made, and the result sets that came back.
Read Post
speedscale

Fixing 403 auth errors when you replay traffic

Jun 12, 2026 By Ken Ahrens In Speedscale
Trigger warning: this one is about Java, authentication, and Docker Compose files. If that is not your thing, I am sorry, but they are part of life and they are honestly not that hard to work with. Everything here is open source on our GitHub repo, so you can follow along. Recording an authenticated Java flow, replaying it, hitting the dreaded 403, and fixing it with a proxymock recommendation.
Read Post
speedscale

We won't train on your data is not a security architecture

Jun 10, 2026 By Ken Ahrens In Speedscale
Every enterprise contract I’ve signed in the last two years has the same clause. “Vendor will not use Customer Data to train machine learning models.” Sometimes it’s a paragraph. Sometimes it’s a whole section. The language varies but the intent is identical: don’t feed our production data into your AI. I get it. I sign the same clause as a vendor. But here’s what’s been bothering me: that clause is a promise, not an architecture.
Read Post
speedscale

Validate Spring Boot Upgrades with Traffic Replay

Jun 7, 2026 By Speedscale Team In Speedscale
Spring Boot version upgrades—whether moving from 2.x to 3.x, 3.x to 4.x, or even minor bumps like 3.2.5 to 3.3.1—regularly introduce subtle, breaking changes that unit and integration tests miss. JSON serialization shifts, autoconfiguration reordering, and transitive dependency conflicts can silently alter your API contract.
Read Post
speedscale

The AI Code Explosion: Why Your Mocking Strategy is Breaking Down

Jun 4, 2026 By Alan Mon In Speedscale
The rise of AI-assisted coding has transformed how software is built. With tools generating entire features in seconds, the bottleneck is no longer writing code—it’s verifying it. Because AI can generate boilerplate and handle API integrations instantly, more service changes are being pushed into authentication logic, API calls, and configurations. Teams desperately need a way to verify these changes before merging, especially when the code touches external dependencies.
Read Post
speedscale

Logs told me something broke. Traffic showed me what.

Jun 2, 2026 By Ken Ahrens In Speedscale
Here’s a problem I run into constantly: something breaks in production, I can see the 500 errors in my logs, but I can’t reproduce it locally. The trace shows me the dependency graph but not the actual request that failed. This is especially painful in microservices. I was looking at a CNCF example the other day (a simple demo app, like 4 pods) and it already had so many cross-service dependencies that understanding what broke required looking at the whole system at once.
Read Post

Copyright © 2026 OpsMatters™. All rights reserved.