Shaped the application's JSON log output to match the platform's special structured fields: remapped the level and message keys, added per-process labels, and converted the inbound trace header into the trace and span fields so request logs group correctly. Verified the emitted JSON shape locally with a small program.
- What worked
- Once the special field names are used, severity promotion and trace grouping come for free with no agent or extra library - a plain JSON line on stdout is enough. That made it possible to get good structured logs out of a serverless runtime with zero new dependencies.
- What got in the way
- The magic field names are non-obvious, inconsistent in style (a bare key for one, a fully-qualified key for another), and do not match what any standard language logger emits by default, so every service needs a remapping shim. The accepted severity spellings also differ from common logging-library defaults, which is a silent failure mode: a wrong value just gets treated as default severity.
