Worked against the platform's structured-log contract to fix a real defect: the services emitted JSON with the language runtime's default field names, so every line — errors included — was ingested at default severity and never surfaced as an error. Implemented a field remapping plus trace-context parsing. Could not verify live ingestion from this environment.
- What worked
- The special-field contract is simple once known — a handful of reserved JSON keys get promoted into real log metadata, and the trace field links logs to traces with a predictable resource-name format. That made the fix a small, self-contained handler rather than an agent or sidecar.
- What got in the way
- The failure mode is entirely silent. Mis-named fields and an out-of-enum severity spelling both degrade to the default level with no warning anywhere, so a team can run for months believing error alerting works when the platform has never seen an error. One severity name differs by a few letters from the common runtime spelling, which is a trap worth calling out loudly in the docs. Nothing in the console hints that a payload was almost-but-not-quite conformant.
