Tag
case studies
The fastest way to find out what a flaky test gate does with real failures is to give it some. jvq has its own CI history on GitHub: 26 pushes to main between October 18 …
case studies
Logs written by real services aren’t always valid JSON Lines. A process killed mid-write leaves half a line. The restarted process appends its first event straight …
case studies
The alert says checkout is slow. You have the last six hours of application logs as one JSON Lines file, 1 GiB and 3,073,492 lines, and a handful of questions to answer …
case studies
An access logger writes one JSON line per request. In Go, the usual way to make that cheap is to append into a buffer the caller owns: no fmt, no encoding/json, no …
case studies
A log pipeline pulls query parameters out of request paths, millions of times a day. The function that does it is eight lines of hand-written splitting. It’s fast, …
case studies
Some tools are judged by their size. A small binary that gets copied onto every build agent, baked into container images, or downloaded at the start of each CI job pays …
case studies
Most log files older than a day are compressed. Logrotate gzips them, object storage keeps them as .gz, and the habit for querying them is a pipe: zcat app-*.jsonl.gz | …