Observability Never Really Shifted Left
We shifted testing, security, and CI/CD left. Observability stayed in production. With AI writing code faster, validation is the bottleneck.
Browse 32 posts in this category
We shifted testing, security, and CI/CD left. Observability stayed in production. With AI writing code faster, validation is the bottleneck.
Follow an eBPF debugging trail through rustls, Tokio inlining, and an empty map to learn how TLS plaintext gets matched to the right TCP connection.
Teams run inventory, security logs, request routing and billing through OpenTelemetry. Five non-observability uses, and the failure mode of each.
Observability tells you when production is on fire. Capturing and replaying real traffic lets you recreate the incident, verify the fix, and keep it fixed.
See why reliability engineering must span code, testing, telemetry, and incidents as AI agents erase the boundary between pre-production and production.
Synthetic monitoring depends on scripts engineers maintain by hand. Capturing and replaying real production transactions turns customer behavior into tests.
Use OpenCost and proxymock to prove Kubernetes rightsizing lowers cost per successful request without hiding behavior or throughput regressions in testing.
Use Grafana Pyroscope and proxymock with an AI coding agent to find a Go CPU hotspot, preserve API behavior, and verify the performance fix.
How our nettap eBPF agent produced garbage HTTP bodies from kernel iov_iter scatter-gather buffers, and the CO-RE plus task-local storage fix that made it correct.
Choose the desktop proxymock or the hosted cloud trial to get started.