Operations | Monitoring | ITSM | DevOps | Cloud

The latest News and Information on API Development, Management, Monitoring, and related technologies.

Feature Spotlight: Testing GraphQL #graphql #apitesting #developertools #techtutorial #devops

Learn how to resolve failed GraphQL session queries by updating expired tokens before replaying your snapshot. This video demonstrates how to find the GraphQL operation, edit variable values by path, and successfully pass replay checks. Learn more: speedscale.com.

Feature Spotlight: Import & Export to Load Testing Tools #api #postman #openapi #loadtesting #devops

Proxymock allows you to import existing Postman collections, browser HAR files, and OpenAPI specifications to instantly create test requests and mock responses. You can also pull traffic directly from cloud storage buckets, or export your requests into load testing scripts for tools like K6, Gatling, and Locust. Coding agents can even manage these imports and exports using integrated MCP tools. Learn more: speedscale.com.

Feature Spotlight: Session-based Replay #trafficanalysis #api #developertools #techtutorial

This video provides an overview of using Sessions to group traffic by actor credentials, track individual user journeys chronologically, and analyze request flows. It also covers how to check replay readiness for JWT sessions, replay recorded user journeys at their original pace, verify pass/fail counts, and save or sample specific sessions for easy sharing. Learn more: speedscale.com.

Quick Load Testing & Mocking with Proxymock and AI #loadtesting #mocktest #softwaretesting #devops

Learn how to quickly set up a load testing foundation for your Node app using the free ProxyMock tool combined with an AI coding agent. This walkthrough demonstrates how to record traffic, mock dependencies, and analyze latency distribution results in just a few simple steps. Learn more: speedscale.com.

Nobody Wants Your New AI Agent #devops #aiagents #softwaredevelopment #techtrends #ai

DevOps customers are rejecting standalone AI agents and web interfaces in favor of integrating context directly into their existing harnesses, such as Copilot or Claude. Rather than logging into separate tools, developers prefer combining models and technologies within a single context window to streamline software development and debugging. Learn more: speedscale.com.

Load Test One Endpoint, Watch the Rest

What happens to transaction posting when statement traffic gets expensive? That’s the question a bank’s platform team actually needs answered before a busy month-end. It’s also a question most load tests can’t ask, because they turn one dial for the whole recording. Statements get heavier, posting gets heavier, and the average latency across both looks fine right up until customers can’t move money.

FastAPI Shipped Three Breaking Changes in 21 Hours: What to Check

FastAPI released 0.146.0, 0.147.0, and 0.148.0 between Sunday afternoon and Monday morning (UTC), and each one is labeled a breaking change. None of them will crash your app on startup. They change what values your endpoints receive, which is the kind of change that passes CI and then shows up as odd data a week later. At Scout Monitoring, we monitor a lot of FastAPI apps, and a loosely pinned fastapi dependency is the most common way these releases will arrive.
Sponsored Post

Chaos Monkey Won't Find Your Bug

We shipped a chaos feature that never caused any chaos. Our mock server has had a fault-injection effect for years with a straightforward job: withhold the response entirely and see whether the caller copes. Last week I audited it against the actual code path. It had never withheld anything. The handler returned early without writing a response. Go's net/http then did what it is designed to do, which is synthesize a 200 OK and flush the recorded body. Every experiment anybody ever ran with that effect handed the application a perfectly good answer, and every one of them passed.

Observability Never Really Shifted Left

We made software development faster. Now we need to make validation faster, too. For the last decade we have shifted development left. Testing, security, performance, and CI/CD all moved closer to the developer. Observability mostly did not. It still starts after deployment (we covered the incident side of this in Your Observability Stack Found the Fire), which means the people writing the code rarely have meaningful production behavior to observe while they build.