Engineering insights, product updates, and monitoring best practices.
A curated list of books and resources for Site Reliability Engineers — from TCP/IP internals to Linux systems programming. What Google recommends, what I actually studied, and why this knowledge translates directly into higher uptime.
A practical history of browser automation — Selenium, Puppeteer, Playwright — and how the same technology now powers synthetic monitoring that catches what HTTP checks miss.
Set up Oack's MCP server in Claude Code, Claude Desktop, Cursor, or Windsurf in under a minute. Plus: use oackctl from any agent that can run shell commands, and leverage llms.txt for context-aware assistance.
When response times spike, how do you find the bottleneck? Walk through a systematic approach using HTTP timing fractions, TCP metrics, server headers, and percentile analysis to isolate whether the problem is on the network, the CDN, or the origin.
Most monitoring tools stop at HTTP status codes. Oack now captures TCP-level metrics — RTT, retransmits, congestion window — so you can diagnose network issues before they become outages.
Cloud monitoring from cloud regions misses the problems your users actually face. Here's why we built a network that lets you monitor from your own infrastructure.