Use AI and traffic replay to test AI-generated code
Have your coding agent test AI-generated code with proxymock: capture working API traffic, replay it against changes, and inspect the results.
Posts about ai/ml
Browse 47 posts in this category
Reliability Engineering in the AI Era
See why reliability engineering must span code, testing, telemetry, and incidents as AI agents erase the boundary between pre-production and production.
Explain Non-CPU Latency With Prometheus + proxymock
Diagnose a p95 latency regression that CPU profiling cannot explain using Prometheus histograms, then prove the fix with identical proxymock replays.
Reproduce A Rare Retry Path With Loki + proxymock
Find the rare payload that sends a service down a retry path, correlate it to the recorded response, and prove the fix with proxymock replay.
Separate Application Latency From Network Failure With Hubble
Use Cilium Hubble flow evidence and proxymock replay to prove whether a Kubernetes timeout came from your code, a dependency, or a dropped packet.
Observe Opaque Services With OpenTelemetry eBPF + proxymock
Discover endpoints, RED metrics, and traces in an opaque Kubernetes service with OpenTelemetry eBPF Instrumentation, then replay traffic with proxymock.
Diagnose Serial N+1 API Calls With Tempo + proxymock
Diagnose serial N+1 API calls with Tempo and proxymock. Replay recorded traffic, inspect trace windows, and prove a concurrency fix preserves behavior.
The Pod Was Cheaper. The Service Wasn’t.
Use OpenCost and proxymock to prove Kubernetes rightsizing lowers cost per successful request without hiding behavior or throughput regressions in testing.
Flamegraphs Find It. Replay Proves It.
Use Grafana Pyroscope and proxymock with an AI coding agent to find a Go CPU hotspot, preserve API behavior, and verify the performance fix.