To get the latest product updates delivered to you, add the URL of this page to your feed reader.
September 20, 2019
Beta release: Stackdriver Logging now offers partitioned tables for exports to BigQuery. For details, go to Partitioned tables.
September 10, 2019
Stackdriver Logging now lets you save your advanced log queries to a Saved Searches library, where they can be managed and shared. Go to Saved searches for details.
When creating a new Google Kubernetes Engine (GKE) cluster, Stackdriver Kubernetes Engine Monitoring is now the default Stackdriver support option. This is a change from prior versions where Stackdriver Logging and Stackdriver Monitoring were the default Stackdriver support option. For more information, see Overview of Stackdriver support for GKE.
April 23, 2019
The maximum size of a log entry has been increased to 256 KB from 100 KB. For details on logging usage limits, go to Quotas and limits.
April 15, 2019
A new Windows version (v1-9) of the Stackdriver Logging agent is now
available. The new version saves the agent service logs on disk for easier
troubleshooting and supports the
config.d configuration extension directory.
March 15, 2019
Stackdriver agents are subject to an updated deprecation policy. As part of this transition, the next major version of the Stackdriver Monitoring and Stackdriver Logging agents will stop supporting operating systems that are at the end of their lifecycle, as well as some third-party agent plugins.
February 22, 2019
You now have two choices for the access control model when creating a cloud Stroage bucket: bucket-only (new) and object-level. Select Set object-level and bucket-level permissions as the access control model during bucket creation if you intend to use the bucket as a sink destination. See Errors exporting to Cloud Storage
January 22, 2019
In the Stackdriver Logging API, log sinks, metrics, and exclusions have two new output-only fields: create time and last update time. See LogSink for an example. If this information isn't available for older resources, these fields aren't present.
December 03, 2018
The Logs Viewer has a new option to display a log entry in its resource context. It can also pin a log entry while allowing you to change the display context. See Viewing Logs for details.
November 01, 2018
You can now view error and success metrics for your log sinks using export system metrics.
October 19, 2018
You can now link from certain App Engine request logs to a detailed trace that explains the request's latency. You can also filter log entries according to their latencies, and if they contain detailed trace data viewable by Stackdriver Trace. See Viewing latency in Trace for details.
October 01, 2018
The Logs Viewer can now download up to 300 log entries in JSON or CSV format. See Viewing Logs for details.
September 14, 2018
The format of service account names for older log sinks is being changed so that all log sinks will have consistent service account names. This naming format has already been applied to project-level sinks on BigQuery, Cloud Pub/Sub, and Cloud Storage permission pages. In the coming weeks, this naming format will be applied to organization-level sinks and folder-level sinks, and to sinks listed on the Logs Exports page in the Logs Viewer. There are no associated changes to functionality or granted permissions.
September 05, 2018
Access Transparency logging is now Generally Available. See Overview of Access Transparency for details.
July 25, 2018
Audit logs exports to BigQuery now feature a compact format. On March 1, 2019, the older extended format will be removed.
June 29, 2018
On July 1, 2018 at 00:00 PDT, Stackdriver switches to consumption-based pricing. For more information, see Stackdriver Pricing.
June 26, 2018
You can now immediately disable all logs ingestion. For instructions, see Stopping all logs ingestion.
June 19, 2018
Google Cloud Storage logs streaming time has been reduced from 12 hours to 3 hours. For details, see Using Exported Logs.
June 18, 2018
Between June 18, 2018 at 06:00 PDT and July 1, 2018 at 00:00 PDT, your use of Stackdriver is free. The service tiers have been removed, and you can experience all features without incurring costs. Thereafter, Stackdriver switches to consumption-based pricing. For more information, see Upcoming Pricing.
June 12, 2018
You can now enable and configure your Data Access audit logs using the GCP console. For details, see Configuring Data Access logs.
May 17, 2018
You can now see your Logging usage and estimate your bill according to the new Stackdriver pricing and in advance of billing enforcement. See Estimating your bills for details.
May 08, 2018
You can now specify custom fields in your Logs Viewer log-entry summary lines. See Add custom fields for details.
May 02, 2018
Stackdriver Kubernetes Monitoring is released in Beta for Kubernetes 1.10 clusters running in Kubernetes Engine. The previous Stackdriver support is still available for those who do not opt into this Beta release. This release affects Logging by introducing new monitored resource types and new Kubernetes metrics.
April 10, 2018
You can now specify that the Stackdriver Logging agent converts your payloads to JSON format for certain log inputs. For details on enabling this feature, see Structured Logging.
March 12, 2018
Beginning on June 30, 2018, Stackdriver is switching to consumption-based pricing, including revised quotas. For more information, see Stackdriver Upcoming Pricing.
Logging data retention has been increased to 30 days for all projects.
February 01, 2018
The Logging agent now supports partial success for logs ingestion. Any invalid log entries in a full set will be dropped, and the valid log entries now will be successfully ingested into the Stackdriver Logging API; previously, the full set would have been dropped if it contained any invalid log entries. To enable partial success, upgrade your Logging agent to google-fluentd v1.5.27.
December 13, 2017
Filtering logs by time range is now available in the Logs Viewer. For more information, see Scroll to a time.
December 04, 2017
Logging agent recommendation: VM instances should have at least 1 GB of memory to run the Logging agent.
Google Cloud Platform HTTP(S) load balancing logging now includes logs for rejected requests, such as those due to invalid or expired URL signatures, and aligns httpRequest.requestSize with metrics from the Stackdriver Monitoring API. For more information, see HTTP(S) Load Balancing Logging.
November 29, 2017
Logs-based metrics are now Generally Available. For more information, see Overview of Logs-based Metrics.
Logging agent installation instructions: The checksum validation step for the installation script has been removed. You can see the new instructions on the logging agent installation page.
Logs Viewer update: Fixes a problem related to the daylight saving time transition in the U.K. If you see your logs displaying in the wrong time zone, you can set your default time zone by using the Jump to date drop-down menu to select a different time zone. For more information, see Logs Viewer user interfaces.
November 01, 2017
Pricing changes: Billing for logs overages will begin March 31, 2018. This date extends the one that was previously communicated to give Stackdriver customers more time to apply the exclusion filters feature to control which logs are stored in Logging. Billing for custom and user-defined logs-based metrics is still postponed. For more information, see Stackdriver Pricing.
October 30, 2017
Exclusion filters are now Generally Available. For more information, see Excluding Logs, and the Resource Usage page in the Logs Viewer.
October 24, 2017
gcloud logging command group is now generally available.
logging will be removed at the end of December 2017. For more information,
see gcloud logging.
September 12, 2017
Admin Activity audit logs retention has been extended to 400 days for both the Stackdriver Basic and Premium service tiers. For more information, see Audit log retention.
Logging agent update to 1.5.18-1. Allows enabling JSON detection via
configuration, fixes a problem with string-valued
timestamps, and allows setting the following
August 31, 2017
Logs-based metrics now support extracting values from log entries to create distribution metrics and to populate user-defined metric labels. This lets you create multiple time series in a single logs-based metric. Also, the latency of logs-based metrics has dropped from approximately 5 minutes to 1 minute, so you can respond more quickly to the metrics. For more information, see Overview of Logs-based metrics.
Exclusion filters let you control which logs are kept in Stackdriver Logging. The Resource Usage page in the Logs Viewer breaks down log volume by resource type. For more information, see Excluding Logs.
Logging agent: The Stackdriver Logging agent package has been updated to version 1.5.17. The agent will now send smaller requests, improving log delivery latency and increasing queries per second, which may affect users with high log volumes. Also, the package's bundled Ruby has been updated to version 2.2.7. If you have configuration snippets or extra gems that depend on older Ruby features, you may have to update them.
Pricing changes: The free per-project allotment of logs is being increased from 5 GB to 50 GB. Beginning December 1, 2017, we will enforce the new limits and begin charging for logs kept in Stackdriver Logging above the limits. For more information, see Stackdriver Pricing.
August 23, 2017
Aggregated Exports: Organizations and folders can now export selected log entries from all of their projects with a single sink created in the organization or folder. For more information, see Aggregated Exports.
Timestamp handling. The following changes to log entry timestamps have been
made or are planned.
1. Logging does not modify the user-provided
timestamp field, except to set it to the current time if it is omitted. A
receivedTimestamp, is set to the time Logging
receives the entry.
timestamp field is used to compute the age of log entries and to
enforce the log retention period. Prior to the change, the
receivedTimestamp field is used for that purpose.
3. Logging discards log entries whose
timestamps are more than 24 hours in the future or
are further in the past than the log entry's retention period.
Prior to the change, future timestamps
and very old timestamps are handled in an unpredictable fashion.
For more information, see
July 10, 2017
IAM support for Logging now includes custom roles. For more information, see Logging Access Control.
API Migration. Information about the deprecated v1 API is being removed from general documentation. Note: Obsolete link to migration information removed on December 13, 2017. For updated information, see APIs & Reference.
June 05, 2017
Exported audit logs in BigQuery: The BigQuery schema for exported audit log
entries changed on June 5, 2017. The following audit log components now have
shortened field names when they are exported to
is a breaking change for queries involving these fields. For more information
see Audit log field changes.
Apps Script: You can access your Apps Script logs in Logging.
Logs Viewer: You can more easily expand all fields in a log entry.
May 01, 2017
Data access logs are now available and are user-configurable. See Configuring Data Access Logs.
Aggregated exports of logs: You can now create log sinks in organizations, billing accounts, and folders. Those sinks can export log entries from all included projects. See Aggregated Exports.
v1 API turndown: writeLogEntries: As a final step in the v1 API turndown,
WriteLogEntries method will be shut down on October 1, 2017.
You must migrate any applications that write log entries using the v1 API. You
must also upgrade any manually-installed Logging agents in your
VM instances. Note: Obsolete link to migration information removed on December
13, 2017. For updated information, see APIs &
v1 API turndown: sinks and logs-based metrics: Migrate your remaining v1 export sinks and v1 logs-based metrics. If you do not, Logging will migrate them by mid-July, 2017. Note: Obsolete link to migration information removed on December 13, 2017. For updated information, see APIs & Reference.
April 01, 2017
Resource types: Several new resource types are added, including types for Cloud Bigtable, Cloud Dataflow, and Cloud Container Engine.
March 31, 2017
V1 API turndown: The date of the v1 API turndown has changed. See the release note for May 2017.
Logging agent for Windows: If you install the Logging agent on VM instances running Microsoft Windows, be aware that there are restrictions on the folders used for the installer and the installed agent. For details, Installing on Linux and Windows.
February 06, 2017
Exporting logs from organizations, folders, and billing accounts: The
command-line tool now supports creating log sinks to export audit logs from organizations,
folders, and billing accounts. This feature also supported in the API.
Viewing multiple logs: Previously in the Logs Viewer, you could view a single log or "all logs" from a single resource type. Now you can select any number of logs within a resource type to view, using the log name dropdown menu.
For example, when viewing App Engine applications, the default is now to display log
entries from any of these logs:
request log, and
Resuming log streaming: The Logs Viewer now automatically resumes streaming logs when its browser window or tab is selected. You no longer have to restart streaming when returning to the page.
App Engine Flexible Environment: For App Engine Flexible Environment, the Logs Viewer can now display application log entries ("log lines") inside the log entry for the associated service request. This is similar to the functionality in the App Engine Standard Environment.
Deleting logs-based metrics in alerting policies: Attempting to delete a
that is used in one or more Stackdriver Monitoring alerting policies now fails with the
FAILED_PRECONDITION. You must remove the metric from the alerting policies or
delete the alerting policies prior to deleting the logs-based metric.
Remove daily API quotas: The Logging API no longer includes daily API quotas. The API still enforces short-term (per 100s) quotas on API calls, as displayed in the Stackdriver Logging API dashboard.
Logs retention and source restriction: With the implementation of the Basic and Premium service tiers in December 2016, Stackdriver Logging began enforcing retention and log source restrictions for projects that are in the Stackdriver Basic tier or are not associated with a Stackdriver account. In the Basic tier, log entries are visible for 7 days after they are received, and logs from non-GCP sources, including Amazon Web Services, are rejected.
December 12, 2016
Logs Viewer v2: The Logs Viewer has been migrated to the Stackdriver Logging API v2. For the full documentation, Viewing Logs (v2). Note: Obsolete link to migration information removed on December 13, 2017. For updated information, see APIs & Reference.
New LogEntry fields: Fields
sourceLocation were added to
November 21, 2016
Organizations: The Stackdriver Logging API now allows both projects and organizations to
own logs. A log belonging to an organization is named
Sinks: The Stackdriver Logging API now allows both projects and organizations to own sinks.
In addition, sinks can now export log entries to destinations in other projects. See
October 20, 2016
Logging is generally available to Google Cloud Platform customers. Individual features that are in Alpha or Beta release are marked as such in the documentation.
Pricing: Stackdriver is now available in Basic and Premium service tiers. All existing and new Stackdriver accounts are entered into a 30-day free trial of the Premium Tier. At the end of the trial period, you could lose some functionality you had during the Beta release unless you upgrade to the Premium Tier. For more details, see Pricing.
API v2: The Stackdriver Logging API v2 is generally available, providing a simplified log
format. During a transition period, you can use the same API at either of these two endpoints:
API v1: The Stackdriver Logging API v1 (v1beta3) is deprecated. Users of this API should migrate to the v2 API. The v1 API will be removed from service on March 30, 2017. Note: Obsolete link to migration information removed on December 13, 2017. For updated information, see APIs & Reference.
September 09, 2016
The Google Cloud Logging API is now known as the Stackdriver Logging API. This change does not affect any code.
June 15, 2016
A change to the v2beta1 API might affect some existing code. In the following methods,
projectName has been changed to
The Google Logging API v2beta1 reference documentation now includes code snippets for each
method. For example, see
April 27, 2016
The user documentation has been reorganized. The documentation landing page and the left-side navigation entries have changed. Existing URLs to individual documentation pages will be redirected if necessary.
March 23, 2016
Google Cloud Logging is now Stackdriver Logging, part of the Google Stackdriver suite of products. You can now manage logs from Amazon EC2 virtual machine instances alongside your Google Cloud Platform (GCP) projects. See Logging agent for more details.
February 18, 2016
The logging agent authorization
instructions now recommend storing private-key credentials as
/etc/google/auth/application_default_credentials.json. You do not have to move your existing
January 29, 2016
December 10, 2015
October 22, 2015
The Logs Viewer now has cascading menus for selecting log entries from Google App Engine and Google Compute Engine.
October 13, 2015
See logs-based-metrics to learn how to create Google Cloud Monitoring metrics using logs filters.
The list of log types has been expanded.
September 15, 2015
September 09, 2015
The command-line interface
in the Google Cloud SDK is now named
gcloud beta logging.
August 12, 2015
August 03, 2015
Cloud Logging now has advanced logs filters that let you specify arbitrary Boolean expressions that match on log entries. See Using advanced logs filters in the Logs Viewer, and the Advanced Logs Filters guide.
June 15, 2015
The Logging documentation has been reorganized. The table of contents now groups all information about the logging agent, viewing logs, and exporting logs in individual sections.
May 21, 2015
A new GCP Console UI panel for the logs export feature
was released. The UI lets you export a subset of your logs from a logs service. For example,
you could export
syslog from Google Compute Engine without exporting
April 28, 2015
You can now stream logs from Cloud Logging to Google Cloud Pub/Sub and from there to your own endpoints. This involves changes to logs export. For example, use Cloud Pub/Sub to route logs through Google Cloud Dataflow and into tools like Google BigQuery.
March 19, 2015
The Google Cloud Logging API is now available in Beta release. The API lets you write logs, create logs, and control the export of logs. Client libraries make it easy to use the API in your favorite programming language.
glcoud logging command-line interface, which uses
the API, is now available in Beta release. The commands provide an easy way to perform
administrative tasks such configuring logs export.
Cloud Logging is now available in Beta release, allowing you to configure, visualize, analyze and export your Google Compute Engine and Google App Engine logs.
google-fluentd logging agent runs with
additional operating systems,
including Debian, Ubuntu, Red Hat, and CentOS. A single script installs the agent on any
supported operating system.
google-fluentd logging agent supports
two dozen third-party logs.
January 15, 2015
Beta release: App Engine logs can be exported to Cloud Storage and BigQuery.