Five Ways to Use OpenTelemetry Beyond Observability
Teams run inventory, security logs, request routing and billing through OpenTelemetry. Five non-observability uses, and the failure mode of each.
Posts by Matt LeRay
Co-founder and CTO of Speedscale, expert in Agentic AI and cloud data warehousing. • 9 posts published
From Handwritten Mocks to proxymock: The Complete Loop
Part 10 of Getting Started with Mocks: use proxymock to record real API traffic, inject failures, verify side effects, and expose contract drift.
The Compounding Platform Tax
Security controls rarely break a banking platform alone. Their cumulative divergence from Kubernetes standards creates a compounding maintenance tax.
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.
From Telemetry to Traffic
Compare eBPF, sidecars, telemetry agents, OpenTelemetry, APM, and proxies through an evolving ladder of production visibility.
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.
The Best Model Is a Routing Decision
The best model isn't the smartest — it's whichever should get the next unit of work. Notes from NVIDIA on routing, local models, and the AI factory.
Trace without traces
The trace was sampled out. I found the bug anyway — by filtering recorded traffic on the customer's email instead of a trace ID. Here's how to follow one request across four services with no trace IDs and no OpenTelemetry.
Try Speedscale free
Choose the desktop proxymock or the hosted cloud trial to get started.