Post

Oblique
@oblique.security

Our background jobs were inexplicably slow. We looked at existing tracing, added OTel, and hypothesized. It looked like a database problem: multi-second SQL queries, connection pool exhaustion, lock contention candidates. The fix that @jbrandhorst.com found turned out to be one line of YAML 😅

Johan Brandhorst-Satzkorn@handle.invalid

SREs hate this one YAML annotation: oblique.security/blog/the-per...

oblique.securityThe performance bug hiding in our billing settings | ObliqueHow we spent two months debugging Cloud Run latency, built out our tracing along the way, and learned the fix was one line of YAML.

1 repost1 like

No replies yet.