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.
Co-founder and CTO of Speedscale, expert in Agentic AI and cloud data warehousing. • 9 posts published
Diagnose a p95 latency regression that CPU profiling cannot explain using Prometheus histograms, then prove the fix with identical proxymock replays.
Generate GraphQL tests and mocks from a schema with proxymock, catch failures hidden inside HTTP 200 responses, and flag schema changes before clients break.
Validate Oracle JDK to OpenJDK migrations with traffic replay. Compare API behavior, check TLS connections, and measure repeatable performance results.
Export a recorded API session to Datadog Synthetics with proxymock. Review step limits, variable chaining, credentials, and assertions before publishing.
Load test one endpoint while keeping another steady. See how separate schedules and latency goals reveal slowdowns an overall average can hide.
Part 3 of Getting Started with Mocks: the same seam, now returning refusals, timeouts and nonsense, so the failure paths finally get tested.
A pragmatic comparison of mitmproxy and proxymock for traffic replay. Learn which tool to use for investigative debugging vs developer productivity, how.
Part 7 of Getting Started with Mocks: a fake HTTP server finally runs the real client, so paths, headers, and parsing get tested. Java, Node, Go, Python.
Replay your app's recorded MySQL statements against 8.4 to catch upgrade regressions, then load test the database with the same workload using proxymock.
Choose the desktop proxymock or the hosted cloud trial to get started.