Release Notes

This page documents production updates to Stackdriver Logging. You can periodically check this page for announcements about new or updated features, bug fixes, known issues, and deprecated functionality.

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 LogEntry fields: trace, sourceLocation, and operation.

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 Log 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. Stackdriver Logging does not modify the user-provided timestamp field, except to set it to the current time if it is omitted. A second field, receivedTimestamp, is set to the time Stackdriver Logging receives the entry.
2. The 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. Stackdriver 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 LogEntry and entries.write.

July 10, 2017

IAM support for Stackdriver Logging now includes custom roles. For more information, see Stackdriver Logging Access Control.

API Migration. Information about the deprecated v1 API is being removed from general documentation. For more information, see Migration to V2, which will be kept.

June 5, 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 BigQuery:protoPayload, protoPayload.serviceData, protoPayload.request, and protoPayload.response. This 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 Stackdriver Logging.

Logs Viewer: You can more easily expand all fields in a log entry.

May 2017

Cloud Audit Logging: 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, the v1 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 Stackdriver Logging agents in your VM instances. For more information, see Migration to the v2 API.

v1 API turndown: sinks and logs-based metrics: Migrate your remaining v1 export sinks and v1 logs-based metrics. If you do not, Stackdriver Logging will migrate them by mid-July, 2017. For more information, see Migration to the v2 API.

April 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, see Installing on Linux and Windows.

February 6, 2017

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: ngnix.request, stdout, request log, and stderr.

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.

Exporting logs from organizations, folders, and billing accounts: The gcloud logging 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.

Deleting logs-based metrics in alerting policies: Attempting to delete a logs-based metric that is used in one or more Stackdriver Monitoring alerting policies now fails with the status 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 a list of changes, see Logs Viewer v2 changes. For the full documentation, see Viewing Logs (v2).

List logs: the Stackdriver Logging API now has "list logs" methods: organizations.logs.list and projects.logs.list.

New LogEntry fields: Fields trace and sourceLocation were added to LogEntry.

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 "organizations/[ORGANIZATION_ID]/logs/[LOG_ID]". See organizations.logs.delete.

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 LogSink.

October 20, 2016

Stackdriver 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. For more information, see Migration to the v2 API. The v1 API will be removed from service on March 30, 2017.

September 9, 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, the parameter projectName has been changed to parent: sinks.create, sinks.list, metrics.list, metrics.create.

The Google Logging API v2beta1 reference documentation now includes code snippets for each method. For example, see entries.list.

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 file at /root/.config/gcloud/application_default_credentials.json.

January 29, 2016

The Logs Viewer now lets you view the structure of log entries. You can also show or hide log entries with similar field values.

December 10, 2015

Version 2 of the Cloud Logging API is now available. Among other changes, the V2 API lets you retrieve log entries from Stackdriver Logging using the entries.list method.

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

Added Java examples of Stackdriver Logging API usage. Simplified the authorization code for Java and Python, and the same code now runs on App Engine, Compute Engine, and your development workstation.

September 9, 2015

The command line interface in the Google Cloud SDK is now named gcloud beta logging.

August 12, 2015

The Cloud Logging API and command line interface now support project sinks. A project sink can export log entries from any combination of logs, based on advanced logs filters.

August 3, 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 agent has new, simpler installation instructions. You no longer have to edit the agent's configuration file to install private-key authorization.

The Stackdriver 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 Cloud Platform 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 activity_log.

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.

The gcloud 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.

The 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.

The google-fluentd logging agent supports two dozen third-party logs.

The Logs Viewer refresh brings more search options and quicker access to logs export configurations. Regex-search has been removed as part of this refresh.

The Cloud Logging documentation has been improved with more setup options, simpler procedures, and more examples.

January 15, 2015

Beta release: App Engine logs can be exported to Cloud Storage and BigQuery.

Monitor your resources on the go

Get the Google Cloud Console app to help you manage your projects.

Send feedback about...

Stackdriver Logging