Google Cloud Observability release notes

Dashboard variables and dashboard-level filtering is now GA. Pinned filters and variables can have multiple default values and they support selection of multiple values. For more information, see the following documents:

• Create and manage variables and pinned filters
• Apply a variable to a widget

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.

The capabilities for dashboard-level filtering has been enhanced. You can now configure pinned filters and variables to have multiple default values and support selection of multiple values. You can also create value-only variables and generate the list of possible values for a variable by running a SQL query. These features are in Public Preview. For more information, see the following documents:

• Create and manage variables and pinned filters
• Apply a variable to a widget

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 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
• Incidents for SQL-based alerting policies

You can now use the Monitoring API to configure a metric-based alerting policy to send notifications when incidents are closed. For more information, see AlertStrategy in the Monitoring API documentation.

With the Ops Agent version 2.51.0, you can now collect a set of observability metrics from NVIDIA Data Center GPU Manager (DCGM). For more information, see NVIDIA Data Center GPU Manager (DCGM).

Your App Hub applications are now writing metadata labels. You can use these labels to filter the data displayed by a chart or monitored by an alerting policy. App Hub labels have the prefix of apphub_.

From the context of an App Hub host, you can now view system metrics for your applications. To view system metrics stored in multiple projects, configure the metrics scope of the App Hub host project. For more information, see the following documents:

• Configure a metrics scope
• App Hub overview

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 apply and modify dashboard-wide filters by selecting the filter option within the cell of a table. For example, if a table has a column named zone and a cell that displays us-east5-b, then selecting the filter button in that cell applies the dashboard-wide filter zone: us-east5-b. For more information about filtering your dashboard, see the following documents:

• Add temporary filters
• Add and mange permanent filters and variables

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.

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.

Table and TopList widgets can now display the results of multiple queries. You can also configure the column headers, data alignment, and color-code cells based on how a numeric value compares to a threshold. For more information, see the following documents:

• Display the most recent data in tabular form
• API Example: Dashboard with a TimeSeriesTable widget

The Metrics management page in Cloud Monitoring now shows you the sources of metric reads and lets you exclude unneeded metrics entirely, eliminating the cost of ingesting them. For more information, see View and manage metric usage.

The fleetwide and per-instance Observability tabs on the Compute Engine VM instances page now include charts for GPU metrics the from NVIDIA Management Library (NVML). To view the fleetwide GPU charts, select Compute Engine > VM instances > Observability. To view the GPU charts for a VM instance, select Compute Engine > VM instances, click on the name of a VM instance, and then select Observability. These charts are available only for VM instances with attached GPUs, with both the Ops Agent and the NVIDIA GPU driver installed. For information about configuring these VMs, see About the gpu metrics.

You can now import Grafana dashboards into Cloud Monitoring by using the console. For more information, see Import Grafana dashboards into Cloud Monitoring.

Error Reporting can now analyze log entries that have been routed to a log bucket in a non-global region, provided the log sink is in the same project as the log bucket.

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.

You can now troubleshoot Compute Engine issues involving host events, MIG autoscaling and health-check failures, resource-availability errors, and VM performance by using the new "interactive playbook" dashboards in Cloud Monitoring. You can access the playbook dashboards from the Dashboards page by selecting the GCP category or by filtering for "GCE Interactive Playbook".

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.

Your dashboards will now recommend event types for display. For more information, see Show events on a dashboard.

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 create private uptime checks that issue TCP requests. For more information, see Create private uptime checks.

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.

You can now configure your dashboards to show disruptions in Google Cloud Services. This feature is GA. For more information, see the following pages:

• For event information, see Personalized Service Health events.
• For information about enabling events, see Show events on a dashboard.

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.

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 configure your dashboards to show when incidents were opened. For more information, see Alert events.

In the Monitoring API, you can now configure documentation links for your notifications. For more information, see Links.

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.

You can now pin your event type selections for custom dashboards. Pinning saves your selections to the dashboard configuration, so they are applied when you reopen the dashboard. For more information, see Show events on a dashboard.

Announcing new Open Telemetry samples that show how to instrument your Python and Node.js applications to collect metrics, logs, and traces:

• Python example
• Node.js example

For general instrumentation information and recommendations, and for links to other samples, see:

• Instrumentation and observability overview
• Choose an instrumentation approach

You can now search a trace for keywords. For more information, see Search a trace.

Announcing new Open Telemetry samples that show how to instrument your Python and Node.js applications to collect metrics, logs, and traces:

• Python example
• Node.js example

For general instrumentation information and recommendations, and for links to other samples, see:

• Instrumentation and observability overview
• Choose an instrumentation approach

You can now configure dashboards to display events by using the Monitoring API.

• For event information, see Event types.
• For information about enabling events, see Show events on a dashboard.
• For an example, see API examples: Enable dashboard events and filters.

You can now configure a logs panel widget to display log entries by log view. For more information, see Display logs and errors on a custom dashboard.

Synthetic monitors no longer require that the ingress rule be set to allow all traffic. For more information, see Cloud Function configuration.

A Selenium WebDriver sample is now available for synthetic monitors. For more information, see Selenium WebDriver template.

Broken-link checkers collect screenshots of failing tests in a Cloud Storage bucket. You can configure this feature to collect screenshots for all tests or disable this feature. For more information, see Create a broken-link checker.

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.

Uptime checks now support authentication by using a service account and a generated OpenID Connect (OIDC) token, as an alternative to providing a username and password. For more information, see Create public uptime checks.

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 display events, such as the crash of a GKE pod, on your dashboards. This feature is now GA. This feature is available for dashboards managed by Cloud Monitoring, and for the observability dashboards managed by Compute Engine, Google Kubernetes Engine and Cloud Run.

• For a list of supported events, see Event types.
• For information about enabling events, see Show events on a dashboard.

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.

Alerting policies with a PromQL-based condition are generally available (GA).

You can now create and manage your uptime checks and synthetic monitors by using the Google Cloud CLI. For more information, see Create public uptime checks and Create a synthetic monitor.

Ops Agent version 2.46.0 introduces a new health check, LogPingOpsAgent, an informational payload message written every 10 minutes to the ops-agent-health log. You can use the resulting log entries to verify that the agent is sending logs. For more information, see Agent health checks.

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.

Observability for Google Kubernetes Engine: You can now enable the package of kube state metrics from the Observability tab of a GKE deployment. For more information, see Package: Kube state metrics.

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.

Observability for Google Kubernetes Engine: The collection of kube state metrics is enabled by default for new GKE Autopilot clusters, starting with version 1.27.4-gke.900. For more information, see Package: Kube state metrics.

On your custom dashboards, you can add section widgets that create a table of contents for your dashboard. You can use the table of contents to navigate to a specific section of your dashboard. For more information, see Organize dashboard widgets.

On your custom dashboards, you can group widgets into a single-view widget or into a collapsible group. Single-view widgets let you display one member of the group. For more information, see Organize dashboard widgets.

You can now collect Prometheus metrics from Cloud Run services by using the Managed Service for Prometheus sidecar for Cloud Run.

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 configure the severity of your alerting policies. This field lets you define the severity level of incidents. For more information, see Structure of an alerting policy.

You can now create a broken-link checker, which periodically validates the links contained in your website. This feature is in Public Preview. For more information, see Create a broken-link checker.

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.

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.

Observability for Google Kubernetes Engine: The Observability tab for a GKE cluster adds a dashboard for GPU metrics. The charts on this dashboard are populated only if the cluster has GPU nodes. For more information, see View observability metrics.

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 display events, such as the crash of a GKE pod, on your dashboards. This feature is in Public Preview.

• For a list of supported events, see Events overview.
• For information about enabling events, see Show events on a dashboard.

Observability for Google Kubernetes Engine: The Observability tab for a GKE deployment now shows application performance metrics if the metrics are available. The supported metric sources include Istio, GKE Ingress, NGINX Ingress and gRPC and HTTP metrics collected by using Google Managed Service for Prometheus. For more information, see Use application performance metrics.

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.

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

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 view error groups on your custom dashboards. This feature is GA. For information when using the Cloud Console, see Display logs and errors on a custom dashboard. For information about using the API, see Dashboard with an ErrorReportingPanel widget.

You can now view error groups on your custom dashboards. This feature is GA. For information when using the Cloud Console, see Display logs and errors on a custom dashboard. For information about using the API, see Dashboard with an ErrorReportingPanel widget.

Ops Agent version 2.42.0 introduces support for Compute Engine Arm VMs that are running Ubuntu 22.04 LTS (Jammy Jellyfish). For more information, see Support for Compute Engine Arm VMs.

You can now import your Grafana dashboards into Cloud Monitoring. For more information, see Import Grafana dashboards into Cloud Monitoring.

You can now configure notifications for Google Chat spaces. For more information, see Create and manage notification channels.

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.

Ops Agent version 2.40.0 introduces support for Compute Engine Arm VMs that are running RHEL 9 or Rocky Linux 9. For more information, see Support for Compute Engine Arm VMs.

Ops Agent version 2.39.0 introduces support for Compute Engine Arm VMs that are running Ubuntu 20.04 LTS (Focal Fossa). For more information, see Support for Compute Engine Arm VMs.

Troubleshooting errors with Duet AI assistance is now available in Preview.

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.

You can now add pie charts to your custom dashboards. Support for pie charts is in public preview. For information when using the Cloud Console, see Graph the most recent data with a pie chart. For information about using the API, see Dashboard with a PieChart widget.

Observability for Google Kubernetes Engine: The Observability tab for each of your GKE clusters now includes filters for recommended and configured integrations. To see the recommended integrations for your cluster, select Integrations > Overview. To see the integrations configured for your cluster, select Integrations > Configured.

Observability for Google Kubernetes Engine: You can now enable a curated set of kube state metrics from the Observability tab for your GKE cluster. You can also preview the available charts and metrics before you enable the metrics. For more information, see Package: Kube state metrics.

You can now troubleshoot GKE issues involving CPU and memory utilization by using the new "interactive playbook" dashboards in Cloud Monitoring. You can access these playbook dashboards from the Dashboards list and from the Incident details page associated with alerts you've set up for CPU utilization or memory utilization.

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.

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.

Error Reporting now reports recent application errors for Google Kubernetes Engine services and clusters on a new App Errors tab.

• To view service errors, go to Kubernetes Engine in the Google Cloud console and select Services & Ingress, then select a specific service and click the App Errors tab.
• To view cluster errors, go to Kubernetes Engine in the Google Cloud console and select Clusters, then select a specific cluster and click the App Errors tab.

PromQL alerting for Cloud Monitoring is in Public Preview. You can now use PromQL queries in your alerting policies. You can also migrate your Prometheus alerting rules to Cloud Monitoring alerting rules with a PromQL query, and migrate your Prometheus receivers to Cloud Monitoring notification channels. For more information, see Alerting policies with PromQL.

In the Error Reporting page's resource filter, you can now filter GKE resources by location, cluster, namespace, and container or pod. For more information, see Filter errors.

Observability for Google Kubernetes Engine: Charts on the Observability tab for each of your GKE clusters and workloads now includes an optional fleet ID filter, where applicable. If the current project is a host project for a fleet, the cluster and workload charts show metrics from all projects in the fleet, even if the metrics are hosted in a different project.

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.

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 snooze an alerting policy from an Incident details page related to the alerting policy. For more information, see Snooze an alerting policy.

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.

You can now create synthetic monitors, which let you continuously test the availability, consistency, and performance of your services and application web pages and APIs, by using automated script based tests. Synthetic monitors periodically probe the endpoints of your application and they record whether or not a probe was successful, along with additional data about the request. For more information, see Synthetic monitoring overview.

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

You can now troubleshoot common GKE issues like unschedulable pods and crashlooping containers by using the new "interactive playbook" dashboards in Cloud Monitoring. For information about using these dashboards, see the GKE troubleshooting documentation for unschedulable pods and crashlooping.

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.

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 grant a predefined role that only lets you view and manage incidents. For more information, see Access control: Incidents.

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

Google Cloud Managed Service for Prometheus can now ingest exemplars attached to histogram metrics. Exemplars are commonly used to attach trace data to latency metrics, to help you find the cause of a sudden change in metric values. For information, see Use Prometheus exemplars.

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.

Observability for Google Kubernetes Engine: The Observability tab for each of your GKE clusters now includes metrics for ephemeral storage. For more information, see View observability metrics.

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 preview support for an OpenTelemetry Protocol (OTLP) receiver. You can use this receiver to collect custom metrics and traces from applications written by using OpenTelemetry SDKs. For more information, see Collect OTLP metrics and traces.

Version 2.31.0 of the Ops Agent introduces preview support for an OpenTelemetry Protocol (OTLP) receiver. You can use this receiver to collect custom traces and metrics from applications written by using OpenTelemetry SDKs. For more information, see Collect OTLP traces.

Observability for Google Kubernetes Engine: You can now enable GKE control plane metrics from the Observability tab for your GKE cluster. You can also preview the available charts and metrics before you enable the metrics. For more information, see Configuring collection of control plane metrics.

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.

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.

The Observability tab on the VM instances page for Compute Engine has been enhanced. Disk and Network sections with additional charts have been added. The Integrations > Detected section lets you navigate to the dashboards for the third-party integrations, like Apache or NGINX, that you have configured. The page also includes a set of Recommended Alerts for setting up pre-configured alerting policies for CPU, memory, and disk utilization and for host errors.

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

A new interface for creating charts with Metrics Explorer is in Public Preview. For more information, see Create charts with Metrics Explorer.

You can now configure metric-based alerting policies to send repeated notifications for open and acknowledged incidents. For more information, see Send repeated notifications.

The Cloud Logging API now supports the following region:

• Doha: me-central1

Google Cloud Managed Service for Prometheus: You can use the OpenTelemetry Collector to scrape standard Prometheus metrics and report them to Managed Service for Prometheus. For more information, see Get started with the OpenTelemetry Collector.

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 have Cloud Monitoring send an email that contains a dashboard URL to people or groups in your organization. For more information, see Share dashboards.

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.

You can now use the gcloud CLI to configure a snooze, which prevents Cloud Monitoring from sending notifications or creating incidents during specific time periods. You can also configure a snooze by using the Google Cloud Console and the API. For more information see Create and manage snoozes.

You can now view and list incidents on your custom dashboards. For more information, see Display incidents on a dashboard.

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.

You can now install pre-defined alerting policies for services integrated with Cloud Monitoring from the Monitoring Integrations page and from the Observability tab on the pages for Kubernetes Engine clusters and workloads. For more information about these installable policies, see Install alerting policies.

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.

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.

The Ops Agent now provides Preview support for NVIDIA GPU metrics, including metrics reported from the NVIDIA Management Library (NVML) and the Data Center GPU Manager (DCGM).

When you install the GPU-enabled version of the Ops Agent, NVML metrics are collected automatically. DGCM metrics are available as a third-party integration. For information about configuring the integration, see NVIDIA Data Center GPU Manager. The reference document for Ops Agent metrics includes tables for the NVML metrics and the DCGM metrics.

Error Reporting now reports recent application errors for Google Kubernetes Engine workloads of type Deployment or Pod. Go to Kubernetes Engine in the Google Cloud console, and select Workloads. From the overview list, select an entry with type "Deployment" or "Pod" to see details about the workload, including recent application errors.

The Ops Agent version 2.25.0 supports a receiver for Prometheus metrics. By using this receiver, you can collect Prometheus metrics from applications running on Compute Engine instances. For more information, see Collect Prometheus metrics.

Now the alerting policy can forecast, or predict, that the threshold will be violated within a configurable time window. These policies are designed to monitor constraint metrics like those that record quota, memory, and storage usage. Forecasting alerts is in Public Preview. For more information, see Forecast condition.

Managed Service for Prometheus: Dashboards for exporter integrations are available and automatically installed when you configure the integration. You can also view static previews of dashboards without configuring the integration. For more information, see the exporter documentation at Set up commonly used exporters.

Cloud Logging now supports the following regions:

• US

• EU

For more information, see Data regionality for Cloud Logging.

You can now use the Observability tab on the Kubernetes Engine Workloads page to see the five workloads consuming the most of a resource. For more information, see View cluster and workload observability metrics.

You can use the new Map view on the VM Instances dashboard to visualize the health of the resources in your fleet. Using the map, you can group VMs by resource labels, like "instance group" or "zone", and color the VMs by the value of a metric, like CPU utilization, to highlight hotspots and anomalies in your fleet.

On the Error Reporting page, use the new resource filter to filter error groups by resource type. For more information, see Filter errors.

Error Reporting is a Virtual Private Cloud (VPC) supported service.

Cloud Monitoring now provides a GKE Clusters dashboard for enabling Managed Service for Prometheus on clusters in your project. For more information, see Get started with managed collection.

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

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 add table widgets to custom dashboards that let you limit the number of table rows, persiste specific columns, display only those rows with the highest, or lowest values, and that display a visual indicator of the value as compared to the range of possible values. For more information, see Display data in tabular form on a dashboard.

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.

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.

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.

The Cloud Monitoring Integrations page now provides access to logs collected by logs-enabled integrations from the Details page for each integration.

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.

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.

The set of pre-configured Monitoring dashboards now includes a Microservices gRPC Overview dashboard. If apps in your project emit gRPC metrics, then this dashboard is automatically added to your list of available dashboards.

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.

You can now use Prometheus Query Language (PromQL) when creating charts and dashboards in Cloud Monitoring. For more information, see PromQL in Cloud Monitoring.

The Cloud Logging API now supports the following region:

• Israel: me-west1.

You can now manage Monitoring-specific roles by using the Cloud Monitoring pages in the Google Cloud console. For more information, see Grant access to Cloud Monitoring.

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 GKE Clusters List page now includes a new Observability tab that displays Monitoring data. This tab shows infrastructure health metric trends such as CPU, memory, container restarts and control-plane metrics. It also provides visibility into ingestion into Google Cloud Managed Service for Prometheus and Cloud Logging. For more information, see View observability metrics.

You can now prevent Cloud Monitoring from sending notifications or creating incidents during specific time periods. For general information, see Snooze notifications and alerts. For information about how to create, view, and modify a snooze, see Create and manage snoozes.

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 add table widgets to custom dashboards that let you limit the number of table rows, display only those rows with the highest, or lowest values, and that display a visual indicator of the value as compared to the range of possible values. For more information, see Display data in tabular form on a dashboard.

You can now add user-defined labels to public and private Uptime checks. For more information, see Create public uptime checks.

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 collect Aerospike metrics from the Ops Agent, starting with version 2.18.2. For more information, see Monitoring third-party applications: Aerospike.

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 collect Vault metrics from the Ops Agent, starting with version 2.18.2. For more information, see Monitoring third-party applications: Vault.

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 Flink metrics from the Ops Agent, starting with version 2.18.1. For more information, see Monitoring third-party applications: Flink.

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.

The Logs Explorer now shows an Error Group button for log entries that are part of error groups. Click the button to access grouping details or to change which log entries the Logs Explorer shows. For more information, see Find log entries with error groups.

Managed Service for Prometheus: You can now query Cloud Monitoring metrics by using PromQL. For more information, see Mapping Monitoring metric names to PromQL.

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 Jetty metrics from the Ops Agent, starting with version 2.17.0. For more information, see Monitoring third-party applications: Jetty.

You can now view the configuration of charts on a dashboard while the dashboard is in read-only mode. For more information, see Show the chart configuration.

You can now add, edit, and remove alerting policy user labels by using the Cloud console when you use the preview alerting interface. To configure policy labels, edit the policy and go to the Notifications and name step. For more information, see Create an alerting policy.

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 configure an uptime check to validate a specific JSONpath. For more information, see Validate response data.

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 see more log entries in the Logs Explorer as a result of several style changes.

You can now configure Metrics Explorer and charts on dashboards to display a ratio of metrics by using the Cloud Console. For more information, see Ratios of metrics.

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.

Preview: You can now get notification recommendations and insights for Error Reporting. For more information, see Error Reporting notification recommender and insights.

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.

You can now define template variables and permanent filters for your dashboards. For more information, see Create a template variable or permanent filter.

User-defined labels are now included in PagerDuty, Pub/Sub, Webhooks, and email notifications, and you can also view these labels on the details pages of alerting policies and incidents. To learn how you can create user-defined labels that contain severity information and attach those labels to alerting policies or incidents, see Add severity levels to an alerting policy.

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 WildFly metrics from the Ops Agent, starting with version 2.12.0. For more information, see Monitoring third-party applications: WildFly.

You can now organize your dashboard widgets into collapsible groups. For more information, see Organize dashboard widgets.

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 collect Apache ActiveMQ metrics from the Ops Agent, starting with version 2.11.0. For more information, see Monitoring third-party applications: ActiveMQ.

You can now collect Apache Hadoop metrics and logs 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 metrics and logs from the Ops Agent, starting with version 2.11.0. For more information, see Monitoring third-party applications: HBase.

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

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

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.

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 Apache CouchDB metrics from the Ops Agent, starting with version 2.10.0. For more information, see Monitoring third-party applications: CouchDB.

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

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

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 view information about your user-defined metrics by using the Diagnostics tab located on the Metrics Explorer page. The Diagnostics tab displays summary information about the user-defined metrics your project injests, charts usage metrics, lists all user-defined metrics. You can use features on this page to create alerts, view audit logs, and get detailed information about individual metrics. For more information, see View metric diagnostics.

Using the new Integrations page in the Google Cloud Console, you can now configure third-party application integrations that the Ops Agent supports. The Integrations page provides links to install instructions, displays example dashboards, and lists the metrics and logs that the Ops Agent collects for each integration. For more information, see Manage integrations

You can now save a copy of a chart on a predefined dashboard to one of your custom dashboards by selecting Add to Custom Dashboard from the More Options menu on the chart. When you select a custom dashboard, you also have the option of renaming the copied chart.

Cloud Debugger now has Preview support for VPC Service Controls.

You can now view SLOs on a custom dashboard. For more information, see Display SLOs on a dashboard.

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 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 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 metrics from the Ops Agent, starting with version 2.8.0. For more information, see Monitoring third-party applications: MySQL.

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

Starting with version 2.8.0, the Ops Agent supports Ubuntu 21.10. For more information, see Linux operating systems.

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.

Cloud Monitoring now supports dashboard-wide grouping and filtering. For more information, see Dashboard-wide filters.

You can now view the project-scoped log entries for all projects in a metrics scope on a custom dashboard. For more information, see View logs on a dashboard.

You can now save a copy of a chart from the Observability tab on Compute Engine's VM instance details page to one of your custom dashboards. To save a copy of the chart, select Add to Custom Dashboard from the More Options menu on the chart. You then select a new or existing custom dashboard, and have the option of renaming the new copy of the chart.

You can now collect Apache Web Server metrics from the Ops Agent, starting with version 2.7.0. For more information, see Monitoring third-party applications: Apache Web Server.

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

You can now create an alerting policy from the alert chart dialog on a custom dashboard, and you can create an alerting policy by converting a chart on custom dashboard to an alert chart. For more information, see Alert charts.

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

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.

GKE version 1.20.8-gke.2100 or later offers a Preview of a fully managed metric collection pipeline to scrape Prometheus-style metrics exposed by any GKE workload and send those metrics to Cloud Monitoring for dashboards, alerts, and SLOs. Compared to the Prometheus Stackdriver sidecar, this new pipeline is easy to set up, allows filtering to control cost, supports larger clusters, is fully managed, supports Autopilot and horizontal Pod autoscaling, and offers better pricing. Get started with GKE workload metrics.

Cloud Monitoring dashboards now support displays of data in tabular form. For information about this feature, see Configure tables with the Cloud Console and Configure tables by using the API.

You can now install the Ops Agent on one or more Compute Engine VMs from the Inventory tab of the Monitoring VM Instances dashboard. The dashboard generates Cloud Shell commands you can use to install the Ops Agent (recommended) or the legacy agents (if needed) on the selected VMs.

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

Cloud Monitoring now lets you configure how long Monitoring waits to close an incident when observations stop arriving. For more information, see Closing incidents.

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 collect nginx metrics and logs from the Ops Agent, starting with version 2.1.0. For more information, see Monitoring third-party applications: nginx.

The VM Instances page features enhanced scorecards for VM health. The new scorecards now include both "maintenance" and "system" events that might affect your VMs and agents, along with other metrics and statistics about the health of your VMs. The filtering and sorting of the Inventory table have also been enhanced.

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

When you create a line chart on a dashboard, you can now specify whether the selected metric is charted against the left Y-axis or the right Y-axis. This feature lets you display different metrics with different scales on the same chart. For an API example, see Dashboard with an XyChart and a threshold.

A new UI for creating alerting policies is available in Preview. This interface offers fine-grained control over the selection of the metrics used in alerting conditions. See Managing Alerting Policies for more information.

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.

The API to manage the metrics scope of a Google Cloud project is now in Preview. For more information, see Manage metrics scopes with the API.

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.

The new External HTTP(S) Load Balancers dashboard in Monitoring provides powerful visualizations to help you understand and troubleshoot connectivity issues on your external load balancers.

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.

The VM instances page has a new Processes tab in Preview. This tab adds charts for process metrics to the charts provided by the existing CPU, Memory, Disk, and Network tabs.

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.

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.

Cloud Trace announces that the OpenTelemetry library for Java is now generally available. For information about configuring your Java application to use Open Telemetry, see Java and OpenTelemetry.

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.

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.

You can now display summaries of single-condition alerting policies on a custom dashboard. A policy summary includes a display of the monitored time series, the threshold, and chips that show the number of open incidents and whether the policy is disabled. For more information about Alert charts, see the following pages:

• Managing dashboards by API
• Adding an alerting policy to a dashboard by using the Cloud Console.

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

The Monitoring dashboards page in the Cloud Console now includes a collection of sample dashboards. The sample dashboards provide support for many common applications. You can preview, install, and then customize these dashboards. For more information, see Installing sample dashboards.

Cloud Monitoring is launching a new Observability tab on Compute Engine's VM instance details page. This tab replaces the Monitoring tab. The enhanced Observability tab provides access to logs and greater visibility into CPU, disk, and network metrics.

A JSON editor has been integrated with the dashboard page. In addition to using the JSON editor to change the contents of the dashboard, you can save the current dashboard definition to a local system, and you can upload a dashboard definition to your Google Cloud project. For more information, see Managing dashboards through the Cloud Console.

Cloud Monitoring is introducing metrics scopes. For a Google Cloud project, its metrics scope defines the projects whose metrics the project can view and monitor:

• When you create a project, its metrics scope is set to self.
• You can modify a project's metrics scope to include other Google Cloud projects, or to include AWS accounts. For more information, see Viewing metrics for multiple projects.
• A Google Cloud project can be included in multiple metrics scopes.

For more information about metrics scopes, see Configuring your project for Cloud Monitoring.

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.

Cloud Monitoring has added new ways to interact with charts. You can now select a range of lines displayed on chart, shift the time axis by using your pointer, and have new controls to expand the chart around a specific point in time. Charts displaying distribution data include 50th, 95th, and 99th percentile lines as an optional overlay. For more information, see Exploring charted data.

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 .

The Inventory tab on the Cloud Monitoring VM Instances dashboard now offers the ability to filter and sort the instance table by any combination of columns. In addition, new health scorecards report a variety of metrics and statistics related to the health and status of your VMs and agents.

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

Cloud Trace announces that the OpenTelemetry library for Python is now generally available. For information about configuring your Python application to use Open Telemetry, see Python and OpenTelemetry.

The Cloud Operations for GKE monitoring dashboard now allows you to manage and display service-level objectives (SLOs) that you define for your applications. For more information, see the Managing SLOs section of the Observing your GKE clusters guide.

The Cloud Operations for GKE monitoring dashboard now includes a column called Error logs that displays the number of error logs associated with an entity based on the selected time range. You can also select which columns to display in the tables. For more information, see the Configuring the dashboard tables section of the Observing your GKE clusters guide.

The Cloud Operations for GKE monitoring dashboard now provides a Metrics tab in the resource details panel. This tab also includes a menu option to create a new alert policy. For more information, see Observing your GKE clusters.

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

The Cloud Operations for GKE monitoring dashboard now provides an Alerts tab in the resource details panel. This tab also includes a link to create a new alert policy. For more information, see Observing your GKE clusters.

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.

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.

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 Incident details page has been completely revised, making it easier to investigate and manage incidents. New features include a timeline of incidents, the addition of a chart with time-range controls and a link to Metrics Explorer, a log for recording the investigative history. For more information, see Investigating incidents.

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

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.

A new dashboard editor is available in Preview. The new editor lets you create and edit all dashboard widget types, including gauges, scorecards, and text boxes. With mosaic-mode, you can resize and reposition widgets. The configuration tabs - Basic, Advanced, MQL - let you choose how you want to configure your widgets. For more information, see Custom dashboards.

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.

Enhancements to the VM Details page. A new Event Timeline shows important events as bars on a timeline. Hovering over any event bar displays summary information about the event and provides a link to the Incident Details page for the event.

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.

Enhancements to the pre-configured Monitoring VM Instances dashboard. The inventory table now includes a Logging Agent Status column, and the Logging agent can be installed by using a UI workflow from the table.

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

Alerting is now available for Monitoring Query Language (MQL). For more information, see Alerting policies with MQL.

Cloud Profiler history view is available in beta. For more information, see Viewing historical trends.

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.

Cloud Trace exemplars can now be viewed in Cloud Monitoring. For more information about Trace exemplars, see Cloud Trace exemplars. For more information about viewing exemplars, see Exploring charted data.

Cloud Trace exemplars can now be viewing in Cloud Monitoring. For more information about Trace exemplars, see Cloud Trace exemplars. For more information about viewing exemplars, see Exploring charted data.

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.

The Cloud Trace viewer now supports search by the trace ID. For more information, see Viewing Trace Details.

The new, out-of-the-box Infrastructure Summary dashboard for Compute Engine VMs provides a single-pane-of-glass view into your VM fleet and load balancers. At a glance, you can see the top 5 VMs across a variety of key metrics including memory, CPU, sent/received traffic, latency, disk read/write, and more.

Enhancements to the pre-configured Monitoring VM Instances dashboard. The inventory table now includes a Monitoring Agent Status column, and the Monitoring agent can be installed by using a UI workflow from the table. The Explore tab gives an overview of additional metrics being sent (including agent metrics, custom metrics, and logs-based metrics) as well as a set of quick links to learn more about each type of metric. You can also use the Recommended Alerts button on the dashboard to configure fleet-wide alerts.

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.

SLO monitoring for microservices is now Generally Available in the Cloud Console. This feature lets you create service-level objectives (SLOs) and set up alerting policies to monitor their performance using auto-generated dashboards with metrics, logs, and alerts in a single place. For more information, see SLO monitoring.

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.

Cloud Debugger now lets you canary snapshots and logpoints on your Node.js applications. To learn more, see the Node.js page for setting up Cloud Debugger.

Cloud Debugger now lets you canary snapshots and logpoints on your Python applications. To learn more, see the Python page for setting up Cloud Debugger.

Enhancements to the pre-configured Compute Engine VM Instances dashboard. Compute Engine cross-fleet metrics and detail views specific to CPU, Disk, Memory, and Network are now available. Use filters to narrow down the set of VMs being inspected, and use the time selector or in-chart time selection to change the time window. VMs with the Monitoring agent installed get detailed memory and disk analysis out of the box.

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.

Cloud Monitoring introduces an improved experience for viewing and managing incidents. Improvements include performance optimizations for Workspaces with large numbers of incidents, summary statics, and the ability to filter by alerting policy name, metric type, and resource type. For more information, see Incidents and events.

Cloud Debugger now lets you canary snapshots and logpoints on your Java applications. To learn more, see the Java page for setting up Cloud Debugger.

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.

Monitoring Query Language (MQL) is now available in Beta. MQL is an expressive, text-based interface to Cloud Monitoring time-series data. With MQL, you can create charts you can't create any other way. You can access MQL from both the Cloud Console and the Monitoring API. For more information, see Introduction to Monitoring Query Language.

The Cloud Profiler Node.js agent now supports release 12 of Node.js. See Profiling Node.js applications for information on configuring your Node.js application.

You can now write time-series data for custom and Prometheus metrics at the rate of 1 data point every 10 seconds. This was previously limited to 1 point every minute.

You can now use OpenTelemetry with Go and Node.js to instrument your applications running on GKE and Compute Engine.

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.

Stackdriver Monitoring agent version 6.0.0 is now available for the following distributions:

• CentOS 7
• Ubuntu LTS 16.04 (Xenial Xerus) and Ubuntu LTS 18.04 (Bionic Beaver)
• Ubuntu Minimal LTS 16.04 (Xenial Xerus) and Ubuntu Minimal LTS 18.04 (Bionic Beaver)
• Amazon Linux AMI (except Amazon Linux 2.0 AMI)

Starting in version 6.0.0, the Stackdriver Monitoring agent is available for the Ubuntu 19.10 (Eoan Ermine) distribution.

Beta release: Export of Stackdriver Trace data to BigQuery. For more information, see Managing Trace exports.

Stackdriver Monitoring agent version 6.0.0 is now available for the Debian 9 distribution.

You can now send notifications from your alerting policies to Cloud Pub/Sub topics. For more information, see Notification options.

Stackdriver Monitoring agent version 6.0.0 has been released to the CentOS 8 distribution.

Starting in version 6.0.0, the Stackdriver Monitoring agent is available for the Debian 10 distribution.

Stackdriver Monitoring Agent version 6.0.0 is now available, and the release will gradually roll out to the various Linux distributions. This version is built on a fork of collectd version 5.8.1 and includes the following changes:

• drops support for various third-party integrations.
• changes the file path for configuring an HTTP proxy when installing the agent.

Stackdriver Monitoring agent version 6.0.0 is now available for the SUSE and SUSE Linux Enterprise Server (SLES) Linux distributions.

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.

Integration of Stackdriver Trace with Virtual Private Cloud Service Controls is now beta. For more information, see VPC Service Controls documentation.

Strackdriver Profiler supports Istio on Google Kubernetes Engine for Go, Java, Python, and Node.js services. This feature is now in Beta.

Integration of Stackdriver Profiler with Virtual Private Cloud Service Controls is now beta. For more information, see VPC Service Controls documentation.

The Stackdriver Monitoring Dashboard API is now in Beta release. You can use this feature to programmatically manage your dashboards and charts. See Managing dashboards by API for documentation, and Dashboard for reference material.

Stackdriver Monitoring in the Cloud Console is in beta release. Your configuration information, such as uptime checks and alerting policies, is accessible and changeable, from the Cloud Console and from the classic Stackdriver Monitoring Console. For more information about the beta, see Monitoring in the Google Cloud Console.

The Trace list page has a new menu-driven filtering solution that is in Beta release testing. For more information, see Finding and viewing traces.

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.

The Service Monitoring API is now in Beta release. You can use this feature to create services, set service-level objectives (SLOs), and create alerting policies to monitor your SLOs. See Service monitoring for documentation, and services for reference material.

Stackdriver Debugger has an updated and expanded quickstart guide showing how to install the agent and debug an app while it's in production. See the Debugger Quickstart guide for more information.

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 Monitoring has two new uptime check features: SSL certificate validation and regex negation content matching.

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.

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.

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.

Java 11 is now supported. For more information, see Profiling Java.

API

Error events written as instances of ReportedErrorEvent generate properly formatted error messages in Stackdriver Logging.

Stackdriver Workspace creation is now a one-step operation.

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.

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.

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.

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.

Python is now supported. For more information, see Profiling Python.

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.

The Stackdriver Monitoring Agent now supports Ubuntu 18.04 LTS ("Bionic Beaver").

Error detection for Python applications has been improved. You might see more newly detected error groups or receive more notifications.

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.

Go 1.11 for App Engine standard environment is now supported. For more information, see Profiling Go.

Documentation for using OpenCensus to capture custom metrics in Java applications is now available. See Custom metrics with OpenCensus for more information.

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.

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.

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

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.

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.

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.

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.

The new Compare To option lets you compare profiles that differ by end time, zone, or service version. For more information, see Comparing profiles.

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.

If you want to minimize the AWS permissions you give to Stackdriver, then see Minimal AWS Permissions.

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

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.

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.

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.

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.

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.

Boolean metrics can now be queried and charted.

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.

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.

Stackdriver Profiler is released in Beta.

Stackdriver Trace Data Access audit logs are now Generally Available. See Stackdriver Trace Audit Logging for details.

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

The AlertPolicy and NotificationChannels APIs are now in Beta release. See Alerting policies and Notification channels for more information.

The Trace Viewer now associates logs entries with trace spans when the LogEntry span_id field is specified. See Integrating with Cloud Logging for details.

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.

The Trace viewer now shows sub-millisecond resolution for Trace spans.

The Trace viewer now displays span annotations and message events written with the Stackdriver Trace API v2. See Viewing Trace Details for more information.

Resolution Status features are now Generally Available. You can now assign a status to your error groups, making it easier to triage errors.

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.

The Stackdriver Trace API v2 is now in Beta release. For a comparison of the v1 and v2 APIs, see Stackdriver Trace API.

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

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

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.

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.

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.

HTTPS(S) Load Balancer metrics are available in Beta release to use in Monitoring. For details, see the Google Cloud 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 Google Cloud 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 Google Cloud loadbalancing metrics and the https_lb_rule monitored resource.

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.

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.

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 Integrating with Cloud Logging.

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

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.

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.

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.

IAM roles: Stackdriver Error Reporting IAM roles are now available. See Error Reporting IAM roles.

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.

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.

Error filters: You can now filter errors by custom text in addition to filtering by time, service, and version.

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

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.

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.

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.

New AWS regions: Monitoring now supports the AWS Canada (ca-central-1) and London (eu-west-2) regions.

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.

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.

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.

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.

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

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.

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.

Cloud Functions: Cloud Functions automatically reports unhandled JavaScript exceptions to Stackdriver Error Reporting.

C++ and Ruby are now supported.

Cloud Console mobile app now supports Error Reporting.

App Engine: Error Reporting is now generally available for Google App Engine standard environment.

API: The Stackdriver Error Reporting API has a new endpoint to report errors: projects.events.report.

The Google Cloud console home page now has an Error Reporting card.

You can now monitor Amazon Web Services (AWS) accounts alongside your Google Cloud projects. Read about Stackdriver Accounts and install the new monitoring agent.

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.

Beta release of Stackdriver Error Reporting.

Charts now have a View Logs option in their settings menu.

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.

First beta release of Google Cloud Monitoring powered by Stackdriver.