Logging release notes

You can now create and manage log scopes by using the Google Cloud CLI, in addition to using the Cloud Console and Terraform. Log scopes are in Public Preview. For more information, see

• Create and manage log scopes
• gcloud logging scopes

You can now use tags to annotate your log buckets and use the tags to manage access to the log buckets. For more information, see Manage log buckets by using tags.

You can now create alerting policies that monitor the results of your SQL queries. For more information about SQL-based alerting policies, see the following documents:

• Monitor your SQL query results with an alerting policy
• Manage incidents for SQL-based alerting policies

You can now include pipe syntax in the SQL queries you run on the Log Analytics page. For more information, see the BigQuery documentation about pipe syntax.

You can now use Terraform commands to a create or update a log scope. For more information, see Create a log scope.

You can now query your log data from the Log Analytics page by using reserved BigQuery slots. For more information, see Query and view logs in Log Analytics.

You can now create and manage your log scopes by using the Logging API in addition to using the Cloud Console. This feature is in public preview. For more information, see Create and manage log scopes.

There is a new Cloud Observability Overview page in the Google Cloud Console. The new page, which you can customize, introduces the Cloud Observability products, and provides information about your logs, dashboards, incidents, and more. This page can help you detect issues in your resources, view relevant events, and view signals that matter to you.

Introducing log scopes. Log scopes are persistent, project-level resources that list a set of resources to be searched for log entries. For example, you might configure a log scope to contain multiple projects and several log views. If you select your log scope when using the Logs Explorer, it displays the log entries that originate in the specified projects and those in the specified log views.

You can create, edit, and delete log scopes. You can also set one log scope as the default log scope, which determines the resources that the Logs Explorer searches for log entries.

For more information, see Create and manage log scopes.

The permissions required to use saved and recent queries have changed. You can also define a location in your default resource settings where saved and recent queries are saved. This location must align with your organization policy.

You can now view the estimated number of byte processed along with the validation status of your SQL query when running queries in Log Analytics. You can use this information to understand the relative volume of data that your SQL query will scan.

You can now analyze your billable log volume when using Log Analytics. This feature is in Public Preview. For more information, see Analyze log volume with Log Analytics.

Ops Agent version 2.48.0 introduces support for Compute Engine VMs that are running Deep Learning VM Images based on Debian 11 (Bullseye). For more information, see Operating systems.

Gauges and scorecards are now available to visualize the results of your SQL queries. For more information, see Chart query results with Log Analytics.

You can now use Terraform commands to attach an IAM role binding to a log view that grants a principal access to the log view. For more information about log views and about controlling access to log views, see Configure log views on a log bucket.

The Logging query language now supports the cast and regexp_extract functions. For more information, see the Logging query language documentation.

Pie charts are now available for visualizing data in the Log Analytics page. For more information, see Change chart type.

You can now configure your aggregated sink to be intercepting, which prevents logs from being passed through the Log Router of child resources. For more information, see Collate and route organization-level logs to supported destinations.

You can now configure and save a Log Analytics chart directly in Monitoring. For more information, see Add charts generated from a Log Analytics query.

Copying log entries is now generally available (GA).

You can now display Log Analytics query results as a table in your Monitoring dashboards by selecting Table as the widget type.

You can now edit Log Analytics charts that are saved to a dashboard directly in the Dashboards page. For more information, see Edit a chart saved to a custom dashboard.

You can now go to the Log Analytics page from the Logs Explorer page by clicking the Analyze results button, which automatically translates the Logging query language query into a SQL query. For more information, see Analyze results.

Charting in the Log Analytics page is now generally available (GA). In addition to features available in the preview, the GA release includes the ability to select none as an aggregation function on a chart.

You can now query for a specific error group in the Logs Explorer and Log Analytics pages by using the error group ID. For more information, see Find error group details for a log entry.

Ops Agent version 2.44.0 introduces the following features:

• Support for Compute Engine VMs that are running Ubuntu 23.10 (Mantic Minotaur). For more information, see Operating systems.
• Support for Compute Engine Arm VMs that are running Debian 12 (Bookworm). For more information, see Support for Compute Engine Arm VMs.
• An option to prevent the agent from collecting self logs and sending them to Cloud Logging. For more information, see Collection of self logs.

You can now specify an inclusion filter or exclusion filter that is applied to the _Default sinks of new resources. For more information, see Configure default filter of _Default sinks.

You can now load saved queries in the Log Analytics page by using the Load button. The Load button lets you edit the query in the Query pane before running the query.

You can now set a custom time interval for charts in the Log Analytics page. The custom time interval can be specified in minutes, hours, or days.

Summarizing log entries with Duet AI assistance is now generally available.

Ops Agent version 2.43.0 introduces support for Compute Engine Arm VMs that are running SLES 15 and OpenSUSE Leap 15. For more information, see Support for Compute Engine Arm VMs.

You can now save charts generated from a Log Analytics SQL query to a custom dashboard. For more information, see Save a chart to a custom dashboard.

Summarizing log entries with Duet AI assistance is now available in Preview.

You can now view your query results as a chart in the Log Analytics page. For more information, see Chart query results with Log Analytics.

Identity and Access Management (IAM) deny policies can now include Cloud Logging permissions. For a list of Cloud Logging permissions that are supported by deny policies, see Permissions supported in deny policies.

Version 2.37.0 of the Ops Agent introduces runtime health checks for errors in the configuration of logging pipelines and in parsing logs. These errors are reported to Cloud Logging. For more information, see Agent health checks.

Ops Agent version 2.36.0 introduces support for Compute Engine Arm VMs that are running Debian 11 (Bullseye). For more information, see Support for Compute Engine Arm VMs.

You can now view logs that are stored in log buckets in different projects by using the Refine scope button in the Logs Explorer. For more information, see Refine scope.

Time ranges are now synchronized between select Logging and Monitoring pages.

The Google Cloud console can now automatically install the Ops Agent for you when you create a VM instance. During the installation process, the Compute Engine VM Manager creates an Ops Agent OS policy that installs the agent and reinstalls it when necessary. For more information, see Install the Ops Agent during VM creation.

You can now create log sinks with user-defined service accounts. For more information, see Configure log sinks with user-managed service accounts.

You can now configure CMEK and a default storage location for individual folders, in addition to organizations. For more information, see Configure default settings for organizations and folders and Configure CMEK for Cloud Logging.

You can now use SQL JOIN and UNION operators in queries on the Log Analytics page. For more information, see Combine data from multiple sources.

You can now customize the time range of your queries in the Log Analytics page by using the time-range selector. There are several time range options, such as preset times, custom start and end times, and relative time ranges. For more information, see Filter by time.

Version 2.31.0 of the Ops Agent introduces built-in support for log rotation. For more information, see Configure log rotation in the Ops Agent.

You can now configure Log Analytics on Cloud Logging buckets and BigQuery linked datasets by using the following Terraform modules:

• google_logging_project_bucket_config

• google_logging_linked_dataset

The Cloud Logging API now supports the following region:

• Doha: me-central1

The Logging Query Language now supports a built-in SEARCH function that you can use to find strings in your log data. The SEARCH function is in preview. For more information, see SEARCH function.

Log-based metrics on log buckets are now generally available (GA). In addition to features available in the preview, the GA release includes the ability to create bucket-level log-based metrics in the Google Cloud console.

Starting with version 2.28.0, the Ops Agent limits the amount of disk space it can use to store buffer chunks. The Ops Agent creates buffer chunks when logging data can't be sent to the Logging API. Without a limit, these chunks might consume all available space, interrupting other services on the VM. When a network outage causes buffer chunks to be written to disk, the Ops Agent now uses a platform-specific amount of disk space to store the chunks.

You can now route logs through the Log Router of another Google Cloud project. The logs can then be managed by the other Google Cloud project, which includes log-based metrics, log-based alerts, and other log sinks. For more information, see Route logs to supported destinations.

The time-range selector in the Logs Explorer has been updated to support a larger set of time range options, such as preset times, custom start and end times, and relative time ranges. For more information, see Use the time-range selector.

You can create log buckets that use Log Analytics and upgrade existing log buckets to use Log Analytics by using the Logging API. For more information, see Create a bucket.

Version 2.25.1 of the Ops Agent introduces health checks. When the Ops Agent starts, it performs a series of checks for conditions that prevent the agent from running correctly. If the agent detects one of the conditions, it writes a message to its health-check log and exits. For more information, see Find Ops Agent troubleshooting information.

Cloud Logging now supports the following regions:

• US

• EU

For more information, see Data regionality for Cloud Logging.

You can now dynamically include your log content in your alert notifications for easier troubleshooting. For more information about extracting log content into labels, see Create a log-based alert (Monitoring API).

The Logs tab available for each cluster on the Kubernetes Engine > Clusters page now includes suggested queries for your logs. For more information about using your GKE logs, see Viewing your GKE logs.

You can now instrument gRPC applications to use Microservices observability.

Pricing for Microservices observability is the same as Cloud Operations Pricing. There are no separate charges for using Cloud Trace, Cloud Monitoring, or Cloud Logging Microservices observability plugins.

To show or hide log entries similar to a log entry displayed in the Logs Explorer, expand the log entry and use the Similar entries menu.

You can now collect Oracle Database logs and metrics from the Ops Agent, starting with version 2.22.0. For more information, see Monitoring third-party applications: Oracle Database.

Using Log Analytics, you can run SQL queries that analyze your log data to generate useful insights. Log Analytics also let you use BigQuery to query your log data. For more information, see Log Analytics.

The Cloud Logging API now supports the following region:

• Israel: me-west1.

Bucket-level log-based metrics are now available in Preview. You can now create log-based metrics that are computed from the logs routed to a specific log bucket. For more information, see Log-based metrics on log buckets.

The Logs Explorer query results now show an icon for log entries that are part of error groups. You can click the icon to view details about the error group, exclude or show only log entries from the error group in the query results, or view related documentation. For more information, see Find log entries with error groups.

You can now collect Couchbase logs and metrics from the Ops Agent, starting with version 2.18.2. For more information, see Monitoring third-party applications: Couchbase.

You can now search your correlated log entries in the Logs Explorer. For more information, see Correlate log entries.

You can now collect SAP HANA logs and metrics from the Ops Agent, starting with version 2.18.1. For more information, see Monitoring third-party applications: SAP HANA.

You can now collect Vault logs from the Ops Agent, starting with version 2.18.1. For more information, see Monitoring third-party applications: Vault.

You can now collect Apache Flink logs from the Ops Agent, starting with version 2.17.0. For more information, see Monitoring third-party applications: Flink.

You can now collect IIS logs and additional metrics from the Ops Agent, starting with versions 2.14.0 (logs) and 2.15.0 (additional metrics). For more information, see Monitoring third-party applications: IIS.

You can now collect Varnish logs and metrics from the Ops Agent, starting with versions 2.16.0 (logs) and 2.15.0 (metrics). For more information, see Monitoring third-party applications: Varnish.

You can now collect Active Directory Domain Services logs and metrics from the Ops Agent, starting with version 2.15.0. For more information, see Monitoring third-party applications: Active Directory Domain Services.

You can now collect Jetty logs from the Ops Agent, starting with version 2.16.0. For more information, see Monitoring third-party applications: Jetty.

You can now see more log entries in the Logs Explorer as a result of several style changes.

You can now hide large amounts of similar log entries from your query results in the Logs Explorer. To learn more, see Hide similar logs.

You can now comment within your Logging queries. For more information, see Logging query language: comments.

You can now do the following in the improved Logs Explorer:

• Use the new plain-text search field and filter menus to construct queries without using the query language
• Customize your date and time format preferences for building queries and to display dates and times in the UI.
• Toggle on and off the default summary fields to see a raw-text view of your logs.

When querying your logs data in the Logs Explorer, you can now select queries from a library, making it easier to explore your data and find logs during time-critical troubleshooting sessions.

The Cloud Logging API now supports the following regions:

• Europe:
  • europe-southwest1
  • europe-west6
  • europe-west8
  • europe-west9
• South America:
  • southamerica-west1

For more information, see Data Regionality for Cloud Logging.

In the Logs Explorer, pinning log entries has been improved and new options to view pinned log entries in different resource contexts have been added. To learn more, see Pin log entries.

Cloud Logging now supports organization policies that can enforce CMEK protection. For information, see CMEK organization policies.

You can now collect RabbitMQ logs from the Ops Agent, starting with version 2.12.0. For more information, see Monitoring third-party applications: RabbitMQ.

You can now collect Apache CouchDB logs from the Ops Agent, starting with version 2.11.0. For more information, see Monitoring third-party applications: CouchDB.

You can now collect Apache Hadoop logs and metrics from the Ops Agent, starting with version 2.11.0. For more information, see Monitoring third-party applications: Hadoop.

You can now collect Apache HBase logs and metrics from the Ops Agent, starting with version 2.11.0. For more information, see Monitoring third-party applications: HBase.

You can now collect Apache ZooKeeper logs from the Ops Agent, starting with version 2.11.0. For more information, see Monitoring third-party applications: ZooKeeper.

You can now collect WildFly logs from the Ops Agent, starting with version 2.11.0. For more information, see Monitoring third-party applications: WildFly.

You can now configure default storage regions and disabled _Default sinks for your Google Cloud organizations and all of their new projects and folders. For details, see Configure default resource settings for Logging.

You can now collect Apache Solr metrics and logs from the Ops Agent, starting with version 2.10.0. For more information, see Monitoring third-party applications: Solr.

You can now collect Apache Kafka metrics and logs from the Ops Agent, starting with version 2.10.0. For more information, see Monitoring third-party applications: Kafka.

You can now collect MongoDB logs from the Ops Agent, starting with version 2.10.0. For more information, see Collect logs from third-party applications: MongoDB.

Your regional preferences, including date and time formatting, are now supported in the Logs Explorer.

Compute Engine resource names, alongside their corresponding resource IDs, are now supported in the Logs Explorer. For details, see View Compute Engine logs.

You can now collect Apache Tomcat metrics and logs from the Ops Agent, starting with version 2.9.0. For more information, see Monitoring third-party applications: Apache Tomcat.

You can now collect PostgreSQL metrics and logs from the Ops Agent, starting with version 2.9.0. For more information, see Monitoring third-party applications: PostgreSQL.

You can now collect Elasticsearch logs from the Ops Agent, starting with version 2.9.0. For more information, see Monitoring third-party applications: Elasticsearch.

Starting with Ops Agent version 2.9.0, you can use the exclude_logs logging processor to prevent the Ops Agent from ingesting specific logs. For more information, see Logging processors.

You can now collect MariaDB metrics and logs from the Ops Agent, starting with version 2.8.0. For more information, see Monitoring third-party applications: MariaDB.

You can now collect MySQL logs from the Ops Agent, starting with version 2.5.0. For more information, see Collecting logs from third-party applications: MySQL.

You can now collect Redis logs from the Ops Agent, starting with version 2.5.0. For more information, see Collecting logs from third-party applications: Redis.

You can now collect Cassandra logs from the Ops Agent, starting with version 2.5.0. For more information, see Collecting logs from third-party applications: Cassandra.

You can now collect Apache httpd logs from the Ops Agent, starting with version 2.4.0. For more information, see Collecting logs from third-party applications: Apache httpd.

The Ops Agent now supports collecting logs from the systemd-journald service, starting with Ops Agent version 2.4.0. For information on configuring the systemd_journald receiver, see Configuring the Ops Agent: Logging receivers.

You can now collect nginx metrics and logs from the Ops Agent, starting with version 2.1.0. For more information, see Monitoring third-party applications: nginx.

You can now use Chef to install and manage the Google Cloud operations suite agents across your fleet of Linux and Windows VMs. For more information, refer to the Chef Integration documentation.

You can now use Puppet to install and manage the Google Cloud operations suite agents across your fleet of Linux and Windows VMs. For more information, refer to the Puppet Integration documentation.

Cloud Logging now lets you control access to individual log entry fields using field-level access control. To learn more, see Field-level access control.

You can now use Cloud External Key Manager keys for organization-level Log Router CMEK. For more information, see Enabling customer-managed encryption keys for Log Router.

You can now install the Logging and Monitoring agents on multiple VMs from the Inventory tab on the Cloud Monitoring VM Instances page. You can select multiple VMs in your fleet for agent installation. The page generates the necessary installation command and provides a link to Cloud Shell, where you can run the command.

The Share link feature for queries in the Logs Explorer now lets you choose whether to include an absolute time range or a relative time range. With an absolute time range, the query includes static time values for the results, so the query always returns the same results. With a relative time range, you can set a value like "last 1 hour", and the results change as time passes.

Preview: Cloud Logging now supports alerts based on matching the content of your logs. When triggered, a log-based alert notifies you that a match has appeared in your logs and opens an incident in Cloud Monitoring. You can create log-based alerts by using the Logs Explorer or the Monitoring API. For more information, see Monitoring your logs and Using log-based alerts.

Cloud Logging lets you copy logs from a Cloud Logging bucket to a Cloud Storage bucket. To learn more, see Copying log entries.

The Logs Explorer Histogram offers new time controls, including zooming and scrolling, to give you more in-depth analysis of your logs data. For details, see Analyzing logs using time controls.

You can now add custom fields in the Logs Explorer to better analyze logs and refine your queries. For more information, see Adding fields to Log fields pane .

You can now install the Cloud Logging agent, Cloud Monitoring agent, and Ops Agent on VMs running OpenSUSE Leap versions 15, 15.1, and 15.2.

You can now provision and manage the Cloud Logging agent on Windows using Ansible. For more information, refer to the Ansible Role for Cloud Ops documentation.

Shared queries are now generally available (GA). To learn more, see Shared queries.

The Google Cloud Ops Agent is now available in Preview. This agent combines logging and metrics into a single agent that is targeted toward specialized logging workloads that require higher throughput and improved resource efficiency. It supports both Linux and Windows Compute Engine VMs.

Cloud Operations now offers the ability to install the Google Cloud Ops Agent via Ansible on Linux and Windows Compute Engine VMs.

Cloud Operations now offers the ability to provision the Google Cloud Ops Agent via Terraform on Linux and Windows Compute Engine VMs.

Cloud Logging now shows the breakdown of log severity levels in the Histogram pane. To learn more, see the Histogram section on the Logs Explorer page.

Compute Engine's VM Instances dashboard now provides an Operations menu. The "View metrics" menu option brings you to the Infrastructure summary dashboard in Monitoring. The "View logs" menu option brings you to the Logs Explorer page in Logging.

Kubernetes Engine's Clusters and Workloads dashboards now provide an Operations menu. The "View metrics" menu option brings you to the GKE Dashboard in Monitoring. The "View logs" menu option brings you to the Logs Explorer page in Logging.

The gcloud commands for managing Agent Policies are now available in beta. For more information, refer to the gcloud documentation for Agent Policies.

In the Logs Explorer, you can now stream your log entries in real time as Cloud Logging ingests them. To learn more, see Streaming logs.

You can now use the Share link button in the Logs Explorer to create and share a shortened URL of your current query. For more information, see Using the Logs Explorer.

By using the new gcloud command and API for live tailing, you can now stream your logs in real time as your applications write them to the Cloud Logging API. To learn more, see Live tailing log entries.

You can now create sinks from within the Logs Explorer and Logs Router pages. To learn more, see Exporting logs with the Google Cloud Console.

In the Logs Explorer you can now download your logs in JSON and CSV to your computer, Google Drive, or view them in a new tab. To learn more, see Downloading logs.

The Ops Agent is now available in Preview. Ops Agent provides a single agent to collect logs and metrics on Compute Engine instances.

Note that the Ops Agent uses new configuration files that are not compatible with the standalone Cloud Monitoring and Cloud Logging agents.

The histogram panel in the Logs Viewer (Preview) now contains a viewport to help you quickly understand the time range of the log entries you're viewing within the Query results pane. To learn more, go to the Histogram panel.

In the Logs Viewer (Preview), you can now pin log entries within the Query results and Histogram panes. To learn more, go to Pinning logs.

In the Logs Viewer (Preview), you can now view a log entry in its resource context. To learn more, go to Viewing a pinned log entry in its resource context.

You can now copy a link to a log entry in the Logs Viewer (Preview). To learn more, go to Copy a link to a log entry.

Cloud Logging now offers the ability to view a history of your ran queries through the Recent queries tab. To learn more, go to the Recent queries section on the Building queries page.

You can now view Cloud Trace information from within the Logs Viewer. To learn more, go to the Trace data section on the Using Logs Viewer (Preview) page.

To help you explore your logs more efficiently, Cloud Logging now provides suggested queries based on the context of your Google Cloud project. For more information, go to Suggested queries.

Beta release: You can now use Logs Buckets to centralize or divide your logs based on your needs. For information about this feature, refer to the Managing logs buckets guide.

Alpha release: You can now use Logs Buckets to centralize or divide your logs based on your needs. For information about this feature, refer to the Managing logs buckets guide. To participate in the alpha or to get notified when Logs Buckets goes beta, fill out the sign up form.

Cloud Logging now contains a Logs Dashboard page that provides a high-level overview into the health of your systems running within a project. To learn more, see Logs Dashboard.

In the Logs Viewer (Preview), you can now save your queries, which can then be viewed and run from the Saved queries tab. For more information, see the Saved queries section on the Building queries page.

Logs Viewer now contains the Logs field explorer panel, which lets you view aggregation-based results for your project's log fields and makes it more efficient to refine queries. To learn more, go to the Logs Viewer (Preview) page.

You can now use regular expressions to query your logs data and create filters. For more information, go to Using regular expressions.

Logs Viewer (Preview) now contains a histogram panel. The histogram panel lets you visualize your logs data to more easily spot patterns and troubleshoot issues. For more information, see Using Logs Viewer (Preview).

Beta release: You can now use the new Logs Viewer (Preview) to view, parse and analyze log data, and refine your query parameters. Go to Logs Viewer interface (Preview) for more information.

Customer-managed encryption keys (CMEK) for the Logs Router are now Generally Available (GA). CMEK lets you create, control, and manage encryption keys to meet your data compliance needs. For details, go to Enabling customer-managed encryption keys for Logs Router.

GA release: You can now use partitioned tables for logs exports to BigQuery. For details, go to Partitioned tables.

Customer-managed encryption keys (CMEK) for the Logs Router are now available in Beta. CMEK lets you create, control, and manage encryption keys to meet your data compliance needs. For details, go to Enabling customer-managed encryption keys for Logs Router.

Beta release: Stackdriver Logging now offers partitioned tables for exports to BigQuery. For details, go to Partitioned tables.

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.

Stackdriver Kubernetes Engine Monitoring is now generally available. Users of the legacy Stackdriver support for monitoring and logging for Google Kubernetes Engine are encouraged to migrate to Stackdriver Kubernetes Engine Monitoring as soon as possible.

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.

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.

You can now view error and success metrics for your log sinks using export system metrics.

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.

The Logs Viewer can now download up to 300 log entries in JSON or CSV format. See Viewing Logs for details.

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.

Access Transparency logging is now Generally Available. See Overview of Access Transparency for details.

You can now immediately disable all logs ingestion. For instructions, see Stopping all logs ingestion.

Google Cloud Storage logs streaming time has been reduced from 12 hours to 3 hours. For details, see Using Exported Logs.

You can now enable and configure your Data Access audit logs using the Google Cloud console. For details, see Configuring Data Access logs.

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.

You can now specify custom fields in your Logs Viewer log-entry summary lines. See Add custom fields for details.

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.

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.

Logging data retention has been increased to 30 days for all projects.

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.

Filtering logs by time range is now available in the Logs Viewer. For more information, see Scroll to a time.

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.

Logs-based metrics are now Generally Available. For more information, see Overview of Logs-based Metrics.

Exclusion filters are now Generally Available. For more information, see Excluding Logs, and the Resource Usage page in the Logs Viewer.

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.

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.

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.

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

Apps Script: You can access your Apps Script logs in Logging.

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

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.

Resource types: Several new resource types are added, including types for Cloud Bigtable, Cloud Dataflow, and Cloud Container Engine.

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.

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.

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.

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.

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.

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: https://logging.googleapis.com/v2beta1/... or https://logging.googleapis.com/v2/....

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.

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.

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.

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

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.

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