Logpipeline

What I’m building

A small C++17 parser that turns structured log lines (level=INFO msg=ok latency_ms=12.5) into typed fields. It is deliberately boring infrastructure — the kind of component you write once and forget until something breaks in production.

Why C++ here

Most of my day-to-day is Go and Python. I wanted something closer to the metal for a parsing hot path: no GC pauses, explicit memory, and a reminder of why higher-level languages exist in the first place. This project is practice, not a production mandate.

What it covers

• Header-only-friendly parser API with optional fields (level, message, latency)
• CMake build with a Makefile wrapper
• Assert-based tests; make test falls back to direct g++ when cmake is not installed

Connection to my day job

Structured logging shows up everywhere in platform work — exporters, sidecars, batch jobs. Understanding how to parse and validate log lines reliably makes you better at designing observability contracts between services, not just shipping features.

Repo

Source lives in the sandbox monorepo under projects/logpipeline/.