This page describes how to view your log entries in real time.
Cloud Logging lets you view your log entries in real time as Logging writes them by using the following features:
Stream logs. Streaming logs is available in the Logs Explorer.
When you view and analyze your logs by using the Logs Explorer,
gcloud logging read, or the API method
entries.list, you are viewing log entries that
Cloud Logging has already stored. In contrast, when you stream
or live-tail log entries, you are viewing log entries as soon as your
applications write them to the Cloud Logging API.
Streaming logs in the Logs Explorer
In the Logs Explorer, you can view your logs data in real time using Stream logs. When you use Stream logs, you can add a query to the Logs Explorer to stream only those logs that match the query.
To stream logs based on a query, add a query to the Query builder pane, and then select Stream logs. As Logging writes the logs data, only those logs that match the query are shown in the Query result pane. If a query isn't provided, Logging shows each log as it's written.
To stop streaming, click Stop streaming, or scroll down in the Query results pane.
Live tailing using the
gcloud command-line tool
Live tailing lets you view your log entries in real time as Cloud Logging
writes them, by using either the
gcloud command-line tool or the Cloud Logging API.
For information on the API method for live tailing, see the entries.tail method.
gcloud alpha logging tail
gcloud alpha logging tail, you need to have Python 3 and
grpcio Python package installed.
For instructions on how to
install Python, see the
For instructions on how to install the Python package manager,
pip, that is
needed to install the
grpcio package, see
The Python Package Installer page.
Complete the following steps to install
gcloud alpha logging tail:
Verify that you have the
gcloudcommand-line tool installed. For instructions on how to install the
gcloudcommand-line tool, see Installing Cloud SDK.
Verify that you're using version 302.0.0 or greater of the
For instructions on updating the
gcloud components update.
gcloudtool alpha components:
gcloud components install alpha
For MacOS, Linux, and Cloud Shell users:
Install gRPC client libraries:
sudo pip3 install grpcio
Set the environment variable
CLOUDSDK_PYTHON_SITEPACKAGESto any value:
Use the following commands to set your Cloud project ID and to authenticate:
gcloud config set project PROJECT_ID gcloud auth login
gcloud alpha logging tailis installed by running the following command:
gcloud alpha logging tail
You are now viewing the log entries for your project as Logging writes them.
For more information on using live tailing, see the
gcloud alpha logging tail reference guide.
Buffering and ordering
Because Logging can receive log entries out of chronological
order, live tailing provides a buffer-window setting so you can balance
the tradeoff between viewing the log entries as they are being written and
viewing them in ascending order. You can set the buffer window
Note the following characteristics of the buffer window:
The default buffer window is two seconds.
Logging delays ingesting the log entries for the duration of the buffer window.
If a log entry is written outside of the buffer window, then Logging returns the log entries as they are received.
When configuring the buffer window, you make a tradeoff between viewing logs as they are ingested and viewing the entries out of order.
||Newest log entries returned, but with more likelihood of them being out of order.|
||A delay of 60 seconds before seeing the entries returned, but most of the logs are returned in ascending order.|
Limits and quotas
The following table lists the limits and quotas for live tailing:
|Limits and quotas||Value|
|Entries returned per minute||60,000
When more the 60,000 entries match a filter, Logging suppresses them and returns the count of suppressed entries in the response.
|Open live-tailing sessions per Cloud project||10|
For a Cloud project that writes lots of entries quickly, your client might be unable to consume them as quickly as they're being written. In this case, Logging limits the total number of entries sent, prioritizing the most recent entries. At the end of the tail session, Logging returns the number of entries that were not displayed due to the limits of the client.