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:

Logs Explorer UI is adding some fields as default summary fields.

For example:

function_name for Cloud Functions or container_name for GKE Container logs.

It would be tremendously helpful and would facilitate the use and readability of these logs, if Cloud Run revisions would have resource.labels.service_name enabled by default, to truly understand from which Run iteration those logs come from.

What you expected to happen:

This feature would add resource.labels.service_name to the default log query results pane and not require user to create a saved query or Edit Summary.

Steps to reproduce:

The lack of functionality is there by default, anyone can see the difference, especially when compared with Cloud Functions that serves similar purpose comparing Cloud Functions default summary fields against what is available in Cloud Run explains the Feature Request on its own.

Additionally, the current custom summary fields are not sticky across session or users, which it only adds the added effort having to manually input the custom field each time someone wishes to have that visibility over the origin of the logs.

[1] https://cloud.google.com/logging/docs/view/logs-explorer-interface#query-results. You can add summary fields to your results, which appear as chips at the beginning of each log entry line. For example, the following image shows query results with the summary field resource.type added to each log entry line: