IssueTracker

This will create a public issue which anybody can view and comment on.

Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.

Problem you have encountered:

In Cloud Run, The top level severity of the correlated logs is always displayed as “INFO” even if the one (or more) instances have a higher severity (e.g. WARNING, ERROR)

The Logs viewer does not change the severity of the top level log entry based on the severity of nested log entries.

What you expected to happen:
Display the Severity of the child log with high priority  (e.g. WARNING, ERROR) Instead if INFO for better monitoring.


Other information (workarounds you have tried, documentation consulted, etc):

https://cloud.google.com/run/docs/logging#correlate-logs