This page provides a combined list of the release notes for products in the Stackdriver suite. You can periodically check these page for announcements about new or updated features, bug fixes, known issues, and deprecated functionality.
You can also see find the release notes for each separate product on the following pages:
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 LoggingStackdriver 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.
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.
August 08, 2019
Stackdriver Monitoring has two new uptime check features: SSL certificate validation and regex negation content matching.
July 31, 2019
Cloud Run and Cloud Run on GKE: Stackdriver Debugger can now be used to debug applications on Cloud Run and Cloud Run on GKE that are written in Node.js, Python, and Java.
May 21, 2019
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.
May 08, 2019
Stackdriver Error ReportingAPI
Error events written as instances of ReportedErrorEvent generate properly formatted error messages in Stackdriver Logging.
Java 11 is now supported. For more information, see Profiling Java.
May 02, 2019
Stackdriver Workspace creation is now a one-step operation. For more information, go to Getting a Workspace quickly.
April 23, 2019
Stackdriver LoggingThe 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.
The OpenCensus library is now generally available as the official library for user-defined metrics in Stackdriver Monitoring. The Custom metrics with OpenCensus page includes samples in Go, Java, Node.js, and Python.
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 26, 2019
Stackdriver Profiler is now generally available. Stackdriver Profiler lets you analyze and understand the performance of your Go, Java, Node.js or Python applications. For more information, see About Stackdriver Profiler.
March 18, 2019
The Uptime Configuration API is now complete and GA. The API, part of the Stackdriver Monitoring API, lets you create, edit and manage uptime checks.
March 15, 2019
Stackdriver LoggingStackdriver 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.
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.
March 12, 2019
Python is now supported. For more information, see Profiling Python.
February 28, 2019
The new Color mode filter option lets you color the flame graph frames by package name, by the metric consumption of the function, or by the metric consumption of the function and its children. For more information, see Color mode.
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
February 08, 2019
The Stackdriver Monitoring Agent now supports Ubuntu 18.04 LTS ("Bionic Beaver").
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.
January 18, 2019
Error detection for Python applications has been improved. You might see more newly detected error groups or receive more notifications.
December 18, 2018
Trace list now limits HTTP method and HTTP status matches to trace root spans. See Filter traces for more details.
You can now filter traces for analysis reports by the full URI, by the URI prefix, or by using trace filter. See Create a new analysis report for details.
December 07, 2018
Go 1.11 for App Engine standard environment is now supported. For more information, see Profiling Go.
December 06, 2018
A mechanism to collect monitoring data from Prometheus clients, which can be deployed as a sidecar in the same Kubernetes pod as a working Prometheus server, is now available. See Using Prometheus for more information.
December 05, 2018
Documentation for using OpenCensus to capture custom metrics in Java applications is now available. See Custom metrics with OpenCensus for more information.
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 16, 2018
The new UI for creating alerting policies is now complete and Generally Available. This interface, based on Metrics Explorer, offers fine-grained control over the selection of the metrics used in alerting conditions. See Managing Alerting Policies for more information.
November 01, 2018
You can now view error and success metrics for your log sinks using export system metrics.
October 31, 2018
Stackdriver Trace enforces consumption-based pricing as of November 1, 2018 at 00:00 PDT. For more information, see Stackdriver Pricing.
On November 1, 2018, Stackdriver Trace begins enforcing a daily trace spans ingestion quota. See Stackdriver Trace Quotas & Limits for details.
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 10, 2018
A new UI for creating alerting policies is available in Beta. This interface, based on Metrics Explorer, offers fine-grained control over the selection of the metrics used in alerting conditions. See Managing Alerting Policies for more information.
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 19, 2018
Stackdriver Kubernetes Monitoring (Beta) for Kubernetes version 1.10.6 and above, restores the managed support for Kubernetes Monitoring. You can also upgrade your existing clusters to this release, no matter which (if any) Stackdriver support they had before. Note the warnings about incompatibilities between the old and new Stackdriver support.
September 18, 2018
The legends for Stackdriver charts have been significantly improved. Legends now support more than one labeled column. The legend provides a selected set of columns as a default, but users can choose the columns they want to see in the legend. All columns are sortable. The legend detects a configuration of columns that exceeds the available space, and provides scrollbars. The resizing of the legends is also improved. For details, see Configuring Legends.
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 10, 2018
"Stackdriver accounts" have been renamed "Workspaces" to reflect their use as a "single pane of glass" through which you view resources from multiple projects and AWS accounts. There is no change in their functionality, but we have improved the documentation for them. For more information, see Workspaces.
September 05, 2018
Stackdriver LoggingAccess Transparency logging is now Generally Available. See Overview of Access Transparency for details.
Billing enforcement for Trace has been postponed to November 1, 2018, rather than the previously announced date of September 30, 2018. You can now estimate your bill for your usage of Trace, according to the new pricing and in advance of billing enforcement. See Estimating your bills for details.
August 02, 2018
The new Weight filter lets you select and graph profiles that consume the most of the profile's measured metric. For more information, see Weight filter.
July 25, 2018
Audit logs exports to BigQuery now feature a compact format. On March 1, 2019, the older extended format will be removed.
July 24, 2018
The new Compare To option lets you compare profiles that differ by end time, zone, or service version. For more information, see Comparing profiles.
June 29, 2018
Stackdriver LoggingOn July 1, 2018 at 00:00 PDT, Stackdriver switches to consumption-based pricing. For more information, see Stackdriver Pricing.
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
Stackdriver LoggingGoogle Cloud Storage logs streaming time has been reduced from 12 hours to 3 hours. For details, see Using Exported Logs.
If you want to minimize the AWS permissions you give to Stackdriver, then see Minimal AWS Permissions.
June 18, 2018
Stackdriver LoggingBetween 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.
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 24, 2018
Any Stackdriver free trials created after May 29, 2018 will expire on June 30, 2018. After June 30, 2018, free trials will be replaced with a free monthly allocation of logs and metrics. For more information about Stackdriver's new consumption-based pricing, see Stackdriver Upcoming Pricing.
May 23, 2018
Custom dashboards and pages for resource groups are now limited to 25 charts. Any dashboards or groups pages with more than 25 charts will continue to work, but you will not be able to add additional charts to them.
May 22, 2018
You can now see your Monitoring usage metrics and estimate your bill for your usage of Monitoring, according to the new Stackdriver pricing and in advance of billing enforcement. See Estimating your bills for details.
May 21, 2018
A new UI for creating conditions in alerting policies is available in Beta. This UI, based on Metrics Explorer, offers fine-grained control over the selection of the metrics used in alerting conditions. See Managing Alerting Policies for more information.
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 15, 2018
The new Focus filter lets you analyze the aggregate resource consumption of a specific function and the proportion of time spent in the function by different callers. For more information, see Using the Focus Filter.
May 11, 2018
If you are using custom Cloud IAM roles, any roles that load Stackdriver Monitoring dashboards now require additional IAM permissions. The monitoring.dashboards.* and monitoring.publicWidgets.* permissions are now public, and custom roles used to load dashboards must now include them. See Stackdriver Monitoring Access Control for more information.
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 LoggingStackdriver 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.
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. The release introduces new monitored resource types and new Kubernetes metrics. The monitoring features are free to customers during the Beta period.
April 26, 2018
You can now use variables in the documentation associated with alerting policies to pull specific details about the alert into notifications, to create playbook information for responders. See Additional documentation tools for more information. The Webhooks and Slack notification channels now receive a copy of this enhanced documentation as part of alert notifications. Additionally, email notifications from alerting policies now use HTML-formatted messages.
April 19, 2018
Boolean metrics can now be queried and charted.
April 17, 2018
The Using Alerting Policies documentation has been updated to provide additional guides and links to sample code for managing alerting policies and notification channels programmatically. The update also removes some obsolete service-tier information.
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.
April 04, 2018
The Trace Viewer now allows you to view trace spans for related Google Cloud Platform projects in one view. See Viewing traces across projects for details.
March 28, 2018
Stackdriver MonitoringStackdriver now loads charts much more quickly, especially when the chart contains a long time span.
Stackdriver Profiler is released in Beta.
Stackdriver Trace Data Access audit logs are now Generally Available. See Stackdriver Trace Audit Logging for details.
March 26, 2018
A new option on the Dashboards menu, Public Charts, lets you see a list of all the shared charts. You can also use this page to remove sharing from a chart. The on-chart indicator that the chart is shared has been removed.
March 12, 2018
Stackdriver LoggingBeginning 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.
Beginning on June 30, 2018, Stackdriver is switching to consumption-based pricing, including revised quotas. For more information, see Stackdriver Upcoming Pricing.
Beginning on June 30, 2018, Stackdriver is switching to consumption-based pricing, including revised quotas. For more information, see Stackdriver Upcoming Pricing.
March 08, 2018
The AlertPolicy and NotificationChannels APIs are now in Beta release.
See Alerting policies and
Notification channels
for more information.
February 27, 2018
The Trace Viewer now associates logs entries with trace spans when the
LogEntry span_id field is specified. See
Viewing Trace Details
for details.
The Trace Viewer now follows your scroll through the span details page, making it easier to see span details of large traces.
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.
January 29, 2018
The Stackdriver email reports that you can configure for your Stackdriver
account have been improved. Issues with the content and the
delivery of reports have been fixed, and the from address for the reports has
been changed from monitoring-noreply@stackdriver.google.com to
monitoring-noreply@google.com. The Utilization section, present only
if the Monitoring Agent is installed,
now lists the 10 groups with the highest utilization, and a new summary row
reports overall utilization for the Stackdriver account.
January 17, 2018
The name of the Monitoring agent process on Windows has been
updated. It now shows up in the system process list as StackdriverMonitoring.
January 12, 2018
The Trace viewer now shows sub-millisecond resolution for Trace spans.
January 09, 2018
The Trace viewer now displays span annotations and message events written with the Stackdriver Trace API v2. See Viewing Trace Details for more information.
January 08, 2018
The performance of the Monitoring dashboards and charts has been improved. Additionally, a new version of Metrics Explorer is available, and the metric-selection interface has been greatly improved, allowing arbitrary label filtering and group-by functionality. This interface is also used for creating dashboard charts, making the process consistent across the two tasks. See Using Charts for more information.
December 19, 2017
Resolution Status features are now Generally Available. You can now assign a status to your error groups, making it easier to triage errors.
December 14, 2017
Alerting events page: An updated implementation has required some user interface changes. The alerting events page (Alerting > Events) no longer shows a heatmap or counts of events in each category.
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 08, 2017
The Monitoring agents for Linux and Windows VM instances now report errors for unrecognized metrics. The errors are written to the agent log on your VM instance. If the Logging agent is also running on the VM instance, then the logs are also available in Stackdriver Logging. The error messages are, "Unsupported collectd plugin/type combination" and "Unsupported collectd ID." Previously, these metrics were dropped silently. See the agent's Troubleshooting Checklist for more information.
November 05, 2017
Documentation for the deprecated Cloud Monitoring API v2 has been removed. The API was turned down in August, 2017.
November 03, 2017
Compute Engine (Go): The support for Go applications on Compute Engine VM instances is in Beta release. Your Go applications should be compiled without the default optimizations, or else Stackdriver Debugger might show incorrect information about your application.
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 31, 2017
The Stackdriver Trace API v2 is now in Beta release. For a comparison of the v1 and v2 APIs, see Stackdriver Trace API.
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
The gcloud logging command group is now generally available. gcloud beta
logging will be removed at the end of December 2017. For more information,
see gcloud logging.
October 19, 2017
Beta release: The Monitoring agent can now export collectd and statsd metrics as Stackdriver custom metrics. For more information, see Custom Metrics from the Agent and the agent's StatsD plugin
October 17, 2017
Beta release: The Uptime Configuration API and uptime metrics are now available. The API, part of the Stackdriver Monitoring API, lets you create and edit uptime checks. The status of your checks is recorded in the uptime metrics.
October 02, 2017
Stackdriver MonitoringCalls to createTimeSeries now fail without writing any data points if the request includes more than one point in the same time series. Formerly, in some cases, one data point would be written in each time series and a status of 500 would be returned by the call.
The Trace viewer now shows parent-child relationships between trace spans. You can expand or collapse the parent spans. See Viewing Trace Details for more information.
September 13, 2017
Object Stores Resources: Google Cloud Storage metrics and Amazon S3 metrics are now separated in the Stackdriver UI into their own service dashboards. The "Object Stores" dashboard is replaced by "Cloud Storage" or "S3", depending on which service you are using.
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.
September 08, 2017
HTTPS(S) Load Balancer metrics are available in Beta release to use in
Monitoring. For details, see the
GCP loadbalancing metrics and
the https_lb_rule monitored resource.
Cloud Interconnect custom dashboards and alert monitoring are available in
Beta release. For details, see the
GCP interconnect metrics and
the interconnect and
interconnect_attachment
monitored resources.
HTTPS(S) Load Balancer metrics are available in Beta release to use in
Monitoring. For details, see the GCP loadbalancing metrics and
the https_lb_rule monitored resource.
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
Stackdriver LoggingAggregated 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
second field, receivedTimestamp, is set to the time 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. 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.
Dashboard filtering: Custom dashboards and resource list pages now support filtering on groups. Each page that supports filtering now has a filter bar under the header where you specify the group.
August 01, 2017
The Trace Viewer now allows you to view associated log entries in line with trace spans and links to VM logs for Google Cloud Load Balancer spans. See the Log Entries section of Viewing Trace Details.
July 10, 2017
Stackdriver LoggingIAM 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.
Heatmaps for distribution metrics: Heatmaps are available in dashboard charts. Select a distribution metric from either the Custom or Logging metric groups and specify Heatmap.
IAM for Stackdriver Monitoring is now complete and GA. New IAM roles include Monitoring Editor and Monitoring Admin, and there is full support for custom roles. For more information, see Monitoring Access Control.
Agent permissions in VM instances: The agent no longer needs the Project Editor IAM role; it only needs the Monitoring Metric Writer role (roles/monitoring.metricWriter). For more information, see Monitoring Access Control.
Windows process metrics now include all processes accessible to the Monitoring agent. See Agent process metrics.
Windows Server 2016 is supported by the current Monitoring agent.
Stacked charts: The order of data streams in stacked charts has been reversed, so that the first stream is on the top and the last stream is on the bottom. This order is consistent with the chart legend and hovercard.
June 05, 2017
Stackdriver Error ReportingIAM roles: Stackdriver Error Reporting IAM roles are now available. See Error Reporting IAM roles.
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 Logging.
Logs Viewer: You can more easily expand all fields in a log entry.
Uptime checks have a new overview and detail dashboards. See Uptime Checks.
Singapore region support:
Stackdriver now supports the Singapore region, asia-southeast1.
Advanced trace filters: The Trace List page and Trace API now allow filtering traces by custom labels, latencies, child spans, and methods in addition to URIs. See Trace Filters.
May 01, 2017
Stackdriver Error ReportingError filters: You can now filter errors by custom text in addition to filtering by time, service, and version.
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 Logging agents in your
VM instances. Note: Obsolete link to migration information removed on December
13, 2017. For updated information, see APIs &
Reference.
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.
New metric and resource types: There are new Cloud Platform metric and resource types, including those for Cloud Bigtable, Cloud Dataflow, Cloud DNS, Cloud Internet of Things, Cloud Pub/Sub, Cloud Spanner, and Stackdriver Logging. Microsoft Windows system and application metrics (iis,mssql, pagefile) are available as Agent metrics and can be used for charting and alerting.
April 02, 2017
v2beta2 API turndown: The deprecated v2beta1 and v2beta2 APIs will be shut down during August 2017.
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
Stackdriver LoggingV1 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.
Time shifting (Beta): You can now compare your current metric data with data from 1 day, 1 week, or 4 weeks ago. See Compare to past in the Advanced options for line chart creation.
Faster chart legends: Charts involving custom and logs-based metrics now have faster legends that include instance names with the metric name where available. You can quickly identify instances and sort the metrics by name.
Faster user interface: Initial page load times have been reduced across the user interface.
Cloud ML: Cloud Machine Learning Engine metrics are available for dashboards and alerting.
Cloud Spanner: Cloud Spanner metrics are available for dashboards and alerting.
Cloud Dataflow: Cloud Dataflow is now integrated with Monitoring. For more details, see the Big Data and Machine Learning Blog.
Monitoring agent: Although the statsd plugin is distributed with the Monitoring agent, there are not yet any instructions for using the plugin with Monitoring.
February 06, 2017
Stackdriver LoggingExporting 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.
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.
Process owner: When sending process metrics, the Stackdriver Monitoring agent now returns a stringified UID if the process owner name is not set. Previously, the agent would not send process owner information, which was then treated by the Monitoring API as malformed input and discarded. Available in stackdriver-agent/5.5.2-359. See Determining the agent version.
Lost input from the Monitoring agent: Malformed data from the Monitoring agent could cause Stackdriver Monitoring to lose well-formed input bundled in the same request. Now, only the malformed input is lost. You do not have to update your agent for this fix.
Selectable uptime check regions: Stackdriver Monitoring now lets you select the geographic region(s) that check your service.
Zipkin tracer compatibility: Stackdriver Trace is now compatible with Zipkin tracers. For more information, see this blog post.
Scatter plots: We've added a new scatter-plot selection tool to the Stackdriver Trace UI. This lets you more quickly identify, view, and compare interesting traces.
January 18, 2017
New AWS regions: Monitoring now supports the AWS Canada (ca-central-1) and London (eu-west-2) regions.
December 12, 2016
Stackdriver LoggingLogs 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.
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.
Account IDs in URLs: Monitoring has added the Stackdriver account ID to its URLs. You can now open multiple tabs for different accounts and more easily share links with coworkers. URLs without the account ID use the most recently accessed Stackdriver account.
December 08, 2016
Incident pages (Beta): See Alerting > Incidents. Each open incident now has a detail page that collects a graph of the incident, links to affected resources, and the comments made on the incident.
Metrics Explorer (Beta): See Resources > Metric Explorer. Select a monitored resource type and metric. You can aggregate data across your instances.
November 21, 2016
Time series: The recommended maximum rate of writing data points to a single time series is changed from 1/sec to 1/min. See Writing metric data.
Chart options: You can now display data as stacked bar charts and stacked area charts, using the Stacked option under Chart Types. Stacked bar charts are automatically aligned to hour boundaries. Stacked area charts work best with metrics received at 1-minute intervals.
New AWS region: Monitoring now supports the AWS region us-east-2.
Chart snapshots: You can now download images of charts in PNG format. Choose Download Image from the More menu. The chart legend is not presently rendered.
Group support for metrics: When charting custom and logs-based metrics, a new Group filter appears under Advanced Options. The effect of the filter is not shown until after you save the chart.
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 DebuggerDebugger GA & logs integration: Debugger is generally available. Debugger now integrates a log panel into the debug view and will remember the last selected location. Additionally, you can insert logpoints dynamically without any rebuilds or restarts. The left and right panels in debug view can now be collapsed for additional viewing space for source.
Cloud Functions: Cloud Functions automatically reports unhandled JavaScript exceptions to Stackdriver Error Reporting.
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:
https://logging.googleapis.com/v2beta1/... or https://logging.googleapis.com/v2/....
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.
GA: Monitoring 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 v3: The Stackdriver Monitoring API v3 is now generally available.
Monitoring agent: A new version of the Stackdriver Monitoring Agent, v5.5.2-349, is available. Its improvements include an update to collectd 5.5.2, support MongoDB 3.0, agent health metrics, and bundled statsd, tail, and network plugins. For more information, see Installing the Monitoring Agent.
Custom metrics: Custom metric descriptors are created as needed when you write time series data. See Auto-creation of custom metrics.
Charting: You can use log scales in your charts, and you can zoom both the x- and y-axes by clicking-and-dragging.
New metrics: New metrics are now available from Cloud Router, BigQuery, and TaskQueues (pull metrics). See the Metrics List.
Creating alerts: We have introduced a new, more streamlined user interface for creating and editing alerting policies.
Analysis Reports: Compare your application's latency profile across time and versions.
September 11, 2016
The Google Monitoring API (v3) is now known as the Stackdriver Monitoring API (v3). This change does not affect any code.
The Monitoring v2 API is now deprecated. It is still named the Google Cloud Monitoring API in APIs & services.
September 09, 2016
The Google Cloud Logging API is now known as the Stackdriver Logging API. This change does not affect any code.
September 08, 2016
C++ and Ruby are now supported.
PHP stack traces are better supported.
August 16, 2016
Cloud Console mobile app now supports Error Reporting.
July 26, 2016
Some documentation pages have moved in the table of contents, but their URLs are the same or have redirections. All agent-related pages are now part of the How-To section, Using the Monitoring Agent. The former "Using Metrics" page has been reorganized into several pages under Using Custom Metrics.
July 18, 2016
App Engine: Error Reporting is now generally available for Google App Engine standard environment.
July 12, 2016
API: The Stackdriver Error Reporting API has a new endpoint to
report errors:
projects.events.report.
June 27, 2016
The GCP Console home page now has an Error Reporting card.
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.
June 09, 2016
The documentation for metrics and custom metrics has been reorganized and extended for the Monitoring API v3. See Metrics, Using Metrics, and Metrics List.
The Stackdriver Monitoring API v3 reference documentation now includes code samples for each method. For example, see metricDescriptors.list. Sample Code will continue to be available on GitHub.
June 06, 2016
Metrics List is now a comprehensive list of all metrics available in Monitoring, including metrics gathered by the monitoring agent and metrics from Amazon Web Services.
April 27, 2016
Stackdriver LoggingThe 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.
The 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.
The Quickstart has been simplified. It now includes setting up a virtual machine instance and installing both the monitoring and logging agents.
March 23, 2016
Stackdriver LoggingGoogle 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.
Google Cloud Monitoring is now Stackdriver Monitoring, part of the Google Stackdriver suite of products.
You can now monitor Amazon Web Services (AWS) accounts alongside your Google Cloud Platform (GCP) projects. Read about Stackdriver Accounts and install the new monitoring agent.
When installing the monitoring agent on an Amazon EC2 VM instance running Microsoft Windows, ignore the following error message if you get it only once after the service is started: "StackdriverAgent is running on an AWS instance but project ID is not set."
March 17, 2016
Stackdriver Error ReportingBeta release of Stackdriver Error Reporting.
The Monitoring API v3 is now available. Users are encouraged to begin upgrading from the Cloud Monitoring API v2. See What's new in the v3 API and look at the new code samples on GitHub.
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 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 29, 2015
Charts now have a View Logs option in their settings menu.
September 15, 2015
Added Java examples of 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 09, 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 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 agent has new, simpler installation instructions You no longer have to edit the agent's configuration file to install private-key authorization.
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 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 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.
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 set-up options, simpler procedures and more examples.
January 15, 2015
Beta release: App Engine logs can be exported to Cloud Storage and BigQuery.
January 07, 2015
First beta release of Google Cloud Monitoring powered by Stackdriver.
