⭐️ fix logging severity for GKE/cloud log explorers#1372
Merged
chris-rock merged 2 commits intomainfrom Feb 6, 2026
Merged
Conversation
Contributor
Configure the logger to output structured JSON with GCP-compatible severity levels. This fixes issue #916 where both INFO and ERROR messages were incorrectly recognized as errors in Google Log Explorer. Changes: - Use JSON encoding by default (Development: false) for proper cloud log parsing - Use "severity" field instead of "level" for log level (GCP requirement) - Map WARN to WARNING (GCP expects WARNING, not WARN) - Map DPANIC/PANIC/FATAL to CRITICAL - Add tests for the GCP level encoder This change is also compatible with AKS and EKS log aggregation. Fixes #916 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Update comments to reference all major cloud providers (GKE, AKS, EKS) instead of just GCP/GKE. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
chris-rock
force-pushed
the
fix/gke-logging-severity
branch
from
5bd2743 to
eda7bc4
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
severityfield instead oflevelfor log level (GCP requirement)WARNtoWARNINGandDPANIC/PANIC/FATALtoCRITICALProblem
Both INFO and ERROR messages were incorrectly recognized as errors in Google Log Explorer, making it hard to filter logs by severity.
Before:
After:
{"severity":"INFO","ts":"2026-02-05T16:19:23+01:00","msg":"test message","key":"value"}Test plan
Fixes #916
🤖 Generated with Claude Code