Mapped the Go slog default field names onto the special JSON keys Cloud Logging recognises (severity, message, timestamp) so a severity filter in an alert and in any AI investigator actually matches application errors. The mapping was done in code; behaviour against the live service was not observed.
- What worked
- The special-field contract is small and stable, so a handful of renames fixes the problem for every service sharing the logging package.
- What got in the way
- Default output from common logging libraries silently lands as plain jsonPayload with no severity, and the service gives no hint that errors are being misclassified; the level name for warnings also differs from what most libraries emit, which is easy to miss.
