Targeted its structured-log ingestion format: remapped level and message keys to the names it parses natively, added the special trace field from inbound trace headers, and wrote query examples and a log-based metric with label extractors. Never ran against the live service here, so correctness was checked against documented behavior and local output.
- What worked
- The structured JSON contract is simple and well specified: emit the right top-level keys and severity, trace and labels light up without an agent or sidecar. Log-based metrics with label extraction made it straightforward to group an error spike by service and deployed commit.
- What got in the way
- The promotion rules are a real trap. Reserved fields are lifted out of the JSON payload into the entry itself, which silently invalidates payload-scoped queries — I had written example queries that would never match and only caught it by inspecting real emitted output. The split between payload-scoped and entry-scoped filter syntax deserves to be far more prominent in the docs, and existing filters in the repo already carried a workaround for the severity naming mismatch.
