Operations | Monitoring | ITSM | DevOps | Cloud

speedscale

Team-Based DLP: Give Each Group Its Own Redaction Rules

Sep 18, 2026 By Matt LeRay In Speedscale
A shared Kubernetes cluster rarely belongs to one team. Payments runs checkout in one namespace, search runs search-api in another, and a risk team runs a scorer somewhere else. One Speedscale forwarder captures API traffic for all of them. Redacting that traffic before it leaves the cluster is what makes it safe to use for testing (the background is in The PII Testing Dilemma). Until now, that forwarder ran exactly one DLP rule. Every team that needed a field redacted had to edit the same JSON document.
Read Post
motadata

Moving Alert and Email-to-Ticket Mail off SMTP AUTH to Microsoft Graph API

Sep 16, 2026 By Ramya Shah In Motadata
Every monitoring alert, scheduled report, and email to ticket conversion in your stack depends on a mailbox. Most monitoring and helpdesk management tools still reach that mailbox the old way. They log in with a username and password over SMTP or EWS. Exchange Online is closing both doors on a published schedule. The tools that fail will fail silently. In this blog, you will: By the end, you can run the change on a weekday afternoon and know nothing went quiet.
Read Post
speedscale

Use AI and traffic replay to test AI-generated code

Sep 15, 2026 By Ken Ahrens In Speedscale
When I ask an AI agent to change code, I also want it to run the application and test what it changed. Asking it to write some tests is a start. But if it invents the expected responses from the same assumptions it used to write the code, those tests can miss the same mistake. Traffic replay gives the agent something concrete to test against: requests and responses captured from a working application.
Read Post

Why Mocks Fail at Scale #softwareengineering #devops #softwaretesting #api #aicoding

Sep 15, 2026 By Speedscale In Speedscale
Mocking for testing starts off easy, but once you scale to multiple teams and AI agents, handcrafted mocks become a serious form of technical liability. Instead of treating mocking as an individual software engineering task, shift your mindset to treat it as a platform engineering task focused on automation and continuously refreshed modern data. Watch to see how adopting technologies like traffic replay to simulate realistic backend sandboxes can transform your modern testing workflow!
View Video
speedscale

eBPF: Correlating rustls Plaintext to TCP Connections Without a File Descriptor

Sep 14, 2026 By Shaun Duncan In Speedscale
In Under the Hood with Go TLS and eBPF, I left socket tracking as an exercise for later. The example used bpf_get_current_pid_tgid() and explicitly excluded concurrent TLS operations. Capturing plaintext was enough for that post. With rustls, later arrived: I could read the HTTP payload perfectly and still attach it to the wrong TCP connection. That’s a frustratingly convincing failure. The request looks right. The response looks right. The application works.
Read Post

Are SOC 2's days numbered? #SOC2 #CodeReview #AICoding #DevOps #SoftwareDevelopment #LLM #SpeedScale

Sep 14, 2026 By Speedscale In Speedscale
As companies adopt AI coding tools, code review processes are breaking down. Traditional compliance methods are slowing teams down, but human engineers aren't going to spend hours reading AI-generated low-level code forever. How will SOC 2 adapt to the era of AI-driven development? Drop your thoughts in the comments and subscribe for more tech insights! Learn more: speedscale.com.
View Video
speedscale

Five Ways to Use OpenTelemetry Beyond Observability

Sep 11, 2026 By Matt LeRay In Speedscale
OpenTelemetry graduated from the CNCF in May 2026 as, in the foundation’s own words, the de facto observability standard. The JavaScript API package alone did 1.36 billion downloads in twelve months. That kind of win has a side effect nobody plans for. Once a wire format is everywhere, has a receiver for every source, a transform language, and an agent your platform team already operates, people start putting things on it that have nothing to do with knowing whether a service is healthy.
Read Post
hyperping

Best API Monitoring Tools in 2026 [31 Analyzed]

Sep 10, 2026 By Leo Baecker In Hyperping
The best API monitoring tools are Hyperping for HTTP and API checks with on-call and status pages, Checkly for API monitoring as code, Postman Monitors for teams that already keep collections in Postman, Datadog for connecting failed checks to traces and logs, Grafana Cloud for teams using k6, Better Stack for checks inside a broader incident workflow, and UptimeRobot for inexpensive availability checks.
Read Post
speedscale

From Handwritten Mocks to proxymock: The Complete Loop

Sep 3, 2026 By Matt LeRay In Speedscale
Handwritten mocks are cheap one at a time. This series built enough of them to show how quickly that stops being true. Nine posts took one package notifier from a function returning "delayed" to a captured response from a real carrier. Along the way, we hand-authored canned successes, failure cases, a spy, a stateful fake, an HTTP server, response fixtures, and contract-drift tests in four languages.
Read Post
How to automate sending and receiving faxes in IT processes? APIs, webhooks, integrations

How to automate sending and receiving faxes in IT processes? APIs, webhooks, integrations

Sep 3, 2026 By OpsMatters In OpsMatters
It's true that fax in 2026 may seem like a technology out of place in today's DevOps environments. However, it's also true that in many regulated industries - it's still a key part of document workflows. The problem isn't necessarily the communication channel itself, but rather how it's handled. Traditional fax requires devices, phone lines, and manual document processing. API integration allows you to migrate this process to a software environment and connect it with existing systems. Curious? Let's dive in.
Read Post
speedscale

Did It Actually Send?

Sep 2, 2026 By Matt LeRay In Speedscale
The notifier has returned a message throughout this series, which made testing almost suspiciously easy. Assert on the return value and you are done. Real notifiers do more than build strings: they send them. Once a message goes to an email provider or SMS gateway, the function may return nothing useful. When that change lands, every existing test loses the value it asserted on. This is part 4 of a ten-part series. The code is in Java, Node.js, Go and Python.
Read Post
speedscale

Make Failure Boring with Mocks

Sep 2, 2026 By Matt LeRay In Speedscale
Every codebase has a failure path nobody has run. Not through laziness, but because reproducing it requires a backend dependency to misbehave on cue. In the package notifier, the carrier must refuse, stall, or return nonsense at the exact moment the test runs. So the retry logic ships unverified and everyone hopes. The seam from post 2 already gives the test control. A seam is a place where you can change what code does without editing that code.
Read Post
speedscale

Test Behavior, Not Choreography

Sep 2, 2026 By Matt LeRay In Speedscale
The spy from post 4 is a sharp tool. Once a test can record every interaction, it is tempting to assert on all of them. The result looks thorough, but it is usually a transcript rather than a useful specification. This post takes a test written that way, makes a change that no customer could possibly notice, and watches the test fail anyway. This is part 5 of a ten-part series. The code is in Java, Node.js, Go and Python.
Read Post
CRM API Rate Limits: What Developers Need to Know Before They Build

CRM API Rate Limits: What Developers Need to Know Before They Build

Sep 2, 2026 By OpsMatters In OpsMatters
Every CRM integration starts the same way. You write some code, test it against a sandbox account with a few hundred contacts, and everything works beautifully. Then you push to production, where the account has 50,000 records and three other integrations pulling data at the same time, and suddenly you're drowning in 429 errors.
Read Post
checkly

We Let AI Agents Rewrite a 92M-Message-a-Day Service in Go. Zero Incidents.

Sep 1, 2026 By Edvinas Janusevicius In Checkly
Our Results Daemon processes about 92 million messages a day. We recently rewrote it from Node.js to Go, and we let Claude Code write it. We wanted to know whether we could trust an agentic rewrite for a critical, high-throughput production service rather than a prototype. It shipped with zero incidents, a 70% reduction in running pods, and a lighter database load.
Read Post

Copyright © 2026 OpsMatters™. All rights reserved.