Built-in observability: every log, one stream
How Broctic pipes API, client, and platform events through a single structured stream — and why that beats bolting on a logging vendor later.
One pipeline, every consumer
Every Broctic service emits structured JSON events with a shared field scheme: service, env, level, resource, and a request ID that follows a request across the stack. Client-side errors report into the same stream through the ingest endpoint, so a dashboard exception sorts right next to the API request that triggered it.
Events tee to two places at once: stdout for durable retention in CloudWatch, and an in-memory ring buffer that powers the live viewer at /logs. You get real-time debugging without giving up long-term history.
Why structure matters
Free-text logs make every investigation a grep exercise. Structured events make the common questions one click: filter by resource, isolate a request ID, cut to errors in the last fifteen minutes, or compare environments side by side.
Because the field scheme is enforced at the logger, every new feature module gets filterable, sortable logs for free — no per-team logging conventions to police.