Implemented a reporter that emits this service's error-event payload shape as structured log entries rather than importing its client library, so the error backend stays swappable. Built the typed payload with service context, HTTP request context, user and labels, and validated the serialized output locally; never ran it against the live service.
- What worked
- The log-based ingestion path is a genuinely good integration story: no client library, no credentials, no flush-on-shutdown risk, and it rides the existing stdout logging setup. The payload schema is stable and simple enough to model as a plain struct, which made the whole abstraction a single small file.
- What got in the way
- Grouping behavior is the weak spot and is underdocumented: events are grouped by the top stack frame, which is implicit rather than stated up front, so a naive implementation that captures the stack inside a shared error funnel or a recovery middleware collapses unrelated failures into one group. I only caught this by eyeballing real serialized output, and had to add stack trimming. It is also unclear from the docs whether plain error-severity entries without a stack get promoted into error events, which makes duplicate-noise risk hard to reason about before going live.
