Cloud Logging
The Logging workspace is a top-level workspace, like Home, Configurations and Resources. It reads Cloud Logging entries for the whole project or for one resource.
Open logs
Section titled “Open logs”There are three ways into the workspace. They differ only in what the query is scoped to:
lopens the Logging workspace on all recent project logs, from anywhere in nuvem. It never looks at your selection.L(shifted) opens Cloud Logging scoped to the one resource the current view has on screen. It works anywhere in the Resources workspace: in a resource list and in a resource detail pane.- In the command palette,
Open project logs(aliaseslogs,logging) is the palette form ofl. TheOpen logs for selected ...entries are the palette form ofL, one per service. Each one is offered only when that service has a resource the jump can resolve.
The help overlay (?) states the difference between l and L on both
entries.
L covers all eleven services: the selected GCE instance, GKE cluster, Cloud
SQL instance, Cloud Run service, Cloud Storage bucket, secret, Cloud Function,
Pub/Sub topic, Pub/Sub subscription, BigQuery dataset, or VPC subnet. It
resolves the target from the view rather than from the raw list cursor.
Inside a Cloud Run revision, it scopes to that revision, not to its service. Inside the Cloud Storage object browser, it scopes to the bucket you
are browsing. With a detail pane open, it follows the pane, not the list
cursor that can still move behind it. If nothing resolves, for example because
the list is empty or no gcloud context is active, the status line says so and
the workspace does not change. A jump that lands, from L or from the
palette, is recorded in navigation history, so Alt-← returns to the resource
you jumped from.
For a resource-scoped query, the workspace header shows the exact filter
string that nuvem built. For the project-wide query, it shows
(all recent project logs). Two of these filters include the project in the
identity they match on. Cloud SQL log entries are keyed by a composite
<project>:<instance> database ID, and a secret’s entries by the full
resource name projects/. If the active context has
no project, these two jumps refuse with a status message instead of sending a
filter that matches nothing.
The workspace only reads logs. It never changes log sinks, metrics, or exclusions.
Follow the tail
Section titled “Follow the tail”The tail runs by default when a query opens. While it runs, the workspace
polls for new entries on the same interval as --poll-interval, one request
at a time. New entries are appended and deduplicated by insert ID. The buffer has a
cap, so memory use stays bounded. If a request fails on a quota or rate limit,
polling waits a growing number of ticks before it retries. Other errors show a
degraded status and keep the last entries on screen.
r asks for the current time window again and keeps the rows already on
screen. If the page comes back unchanged, the view stays as it was. If no
context is active, there is no project to read from, and nuvem fetches
nothing. The rows stay on screen, and the status line reports the missing
context, so you can tell a refused refresh from one that returned the same
page.
Read the entries
Section titled “Read the entries”In the Logging list:
j/kor the arrows move the selection.Enteropens the selected entry’s detail, with its payload and labels.Enter,Esc, orqcloses it.tpauses or resumes the tail.wtoggles line wrapping of long message and payload lines in the entry detail view. With wrapping on, long lines wrap instead of being truncated./edits a client-side search over the loaded entries.Enterapplies it, andEsccancels the draft.ycopies the selected entry, andicopies its insert ID. Both work from the list and from an open entry’s detail.PageUp/PageDownscroll an open entry’s detail.
Narrow the window
Section titled “Narrow the window”Two settings narrow the entries on the server. They change the query that nuvem sends to Cloud Logging, instead of hiding rows it already fetched.
sraises andSlowers the severity floor one rank at a time. The steps stop at either end and do not wrap. The default floor isall, which adds no severity clause.- The digits
0-6pick the time window directly, from1mto24h.Tcycles through the windows, shortest to longest. The default is1h.
The header shows both, as Severity: <floor> and Range: <window> [<digit>].
Severity floor and time window lists every
floor and window.
Search the loaded entries
Section titled “Search the loaded entries”The / search runs over the loaded buffer and understands four forms:
- A bare term is a case-insensitive substring. This is the default.
~termis a fuzzy subsequence./pattern/is a case-insensitive regex.- A leading
!inverts any of them.
While no search is applied, the header lists the ~, /…/ and !
prefixes. Once one is applied, the header names the mode the pattern
selected. A regex that does not compile shows no rows and reports the reason.
Substring is the default so that a bracketed level such as [ERROR] matches
the brackets you typed. As a regex, [ERROR] is a character class.
ARCHITECTURE.md explains this choice, and why a regex search needs the
/…/ form.
Save entries to a file
Section titled “Save entries to a file”Ctrl-S saves the visible entries, after the search filter, to
log-dumps/. That directory sits beside nuvem’s own log
file, and nuvem info prints its path. Each entry becomes one sanitized line,
and nuvem reports the absolute path it wrote. If no entries are visible, it
writes no file. If no log directory resolves, it reports a save failure and
does not fall back to the working directory.
Severity floor and time window
Section titled “Severity floor and time window”The severity floors, lowest to highest:
| Floor | Shows |
|---|---|
all |
every entry; no severity clause is sent (the default) |
DEBUG |
DEBUG and above |
INFO |
INFO and above |
NOTICE |
NOTICE and above |
WARNING |
WARNING and above |
ERROR |
ERROR and above |
CRITICAL |
CRITICAL and above |
ALERT |
ALERT and above |
EMERGENCY |
EMERGENCY only |
The time windows, with the digit that picks each:
| Key | Window |
|---|---|
| 0 | 1m |
| 1 | 5m |
| 2 | 15m |
| 3 | 30m |
| 4 | 1h (the default) |
| 5 | 6h |
| 6 | 24h |
nuvem is released under the MIT License. The source is on GitHub.
nuvem is an independent project, not affiliated with or endorsed by Google. Google Cloud is a trademark of Google LLC.