Cloud Run Logs
A real-time log viewer panel for Cloud Run services with severity filtering, function name filtering, and expandable log entry details.
Cloud Run services and Cloud Functions (2nd gen) write structured logs to Google Cloud Logging. The Cloud Run Logs panel streams these logs directly into your Rift Panel workspace, giving you a live view of what your services are doing without opening the Cloud Console. The panel supports filtering by severity level and function name, making it straightforward to isolate the log entries you care about during development and debugging.
Log Viewer
The log viewer displays a scrollable, time-ordered list of log entries. Each entry shows:
- Timestamp — When the log entry was written, displayed in your local timezone
- Severity — A color-coded badge: gray for DEBUG, blue for INFO, yellow for WARNING, red for ERROR
- Service name — The Cloud Run service or function that produced the entry
- Message — The log message text, truncated to one line in the list view
New log entries appear at the bottom of the list in real time. The viewer auto-scrolls to the latest entry as long as you are already scrolled to the bottom. If you scroll up to review older entries, auto-scroll pauses and a "Jump to latest" button appears so you can resume following the live stream when ready.
The log viewer fetches the most recent 200 log entries on panel open, then switches to a streaming mode that appends new entries as they arrive. The streaming connection uses the gcloud logging tail command under the hood, which provides near-real-time delivery with minimal latency.
Filtering
The filter bar at the top of the panel provides two filtering dimensions:
Severity Filter
A set of toggle buttons lets you show or hide log entries by severity level. All levels are shown by default. Click a severity badge to toggle it off or on:
| Level | Description | Use Case |
|---|---|---|
| DEBUG | Verbose diagnostic information, usually only useful during active development | Development and troubleshooting |
| INFO | Normal operational messages such as request handling and startup events | Operation tracking |
| WARNING | Non-critical issues that may indicate a problem (deprecated API usage, slow queries, etc.) | Proactive monitoring |
| ERROR | Failures that require attention (unhandled exceptions, failed requests, timeouts) | Issue identification |
Severity filtering happens client-side, so toggling levels is instant even with a large number of buffered entries. The filter state is remembered for the lifetime of the panel.
Function Name Filter
The text input next to the severity toggles lets you filter by service or function name. Type a partial name to see only entries from matching services. This is especially useful in projects with many Cloud Run services or Cloud Functions, where the unfiltered log stream can be overwhelming. The filter uses substring matching and is case-insensitive.
Combine severity and function name filters for targeted debugging. For example, filter to ERROR severity and your specific function name to see only errors from a single service.
Log Details
Click on any log entry to expand it and view the full payload. The expanded view shows:
- Full message — The complete log message without truncation
- Structured fields — If the log entry contains JSON structured data, each field is displayed in a key-value table
- HTTP request details — For request log entries, the method, URL, status code, latency, and user agent are shown
- Trace and span IDs — If Cloud Trace integration is active, the trace ID is displayed as a clickable link to the Cloud Console trace viewer
- Labels — Any custom labels attached to the log entry
You can copy the full JSON payload of any log entry to the clipboard using the copy button in the expanded view. This is useful for sharing specific log entries in bug reports or pasting them into other tools for analysis.
Prerequisites
The Cloud Run Logs panel requires the Google Cloud CLI to be installed and configured:
- gcloud CLI — Install the Google Cloud SDK and ensure
gcloudis on your PATH. - Authentication — Run
gcloud auth login. The panel uses your default credentials to access Cloud Logging. - Project selection — The panel reads the active project from your
gcloud config. Ensure the correct project is set withgcloud config set project <PROJECT_ID>. - IAM permissions — Your account needs the
logging.logEntries.listpermission, typically granted by the Logs Viewer role (roles/logging.viewer).
Log streaming uses gcloud logging tail, which requires the gcloud beta component. If streaming does not start, run gcloud components install beta in a terminal session.