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:
]]>Audit Logging now populates the status.details field in the audit log with the google.rpc.ErrorInfo and google.rpc.Help proto payload types in cases where an API returns an error status and that status includes one of those types in the details field.
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
]]>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.
A weekly digest of client library updates from across the Cloud SDK.
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:
]]>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:
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:
]]>A weekly digest of client library updates from across the Cloud SDK.
A weekly digest of client library updates from across the Cloud SDK.
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.
]]>Ops Agent release 2.51.0 adds support for Compute Engine Arm VMs that are running Rocky Linux 8.
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:
Ops Agent release 2.51.0 adds support for Compute Engine Arm VMs that are running Rocky Linux 8.
]]>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.
A weekly digest of client library updates from across the Cloud SDK.
The user interface for configuring which events to show on a dashboard has been simplified. For more information, see Show events on a dashboard.
]]>You can now use Terraform commands to a create or update a log scope. For more information, see Create a log scope.
]]>The layout of the Logs Explorer page has been changed. For more information, see View logs by using the Logs Explorer.
The pricing for vended network logs has changed. For more information see the following:
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:
The layout of the incident detail page has been updated. You can now view related incidents, and switch between viewing only the time series that caused the condition to be met and viewing all time series that the alerting policy evaluated. For more information, see Incidents for metric-based alerting policies and Incidents for log-based alerting policies.
]]>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.
A weekly digest of client library updates from across the Cloud SDK.
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:
]]>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.
]]>A weekly digest of client library updates from across the Cloud SDK.
Cloud Monitoring has ended support for the ingestion of AWS CloudWatch metrics by using AWS connector projects. This is a breaking change. For information about this deprecation, see Deprecations: AWS CloudWatch metrics in Connector projects.
You can continue to collect AWS CloudWatch metrics by using the open source Prometheus CloudWatch exporter and the Ops Agent. For information about this solution, see Collect AWS CloudWatch metrics by using the Prometheus CloudWatch exporter.
]]>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.
]]>A weekly digest of client library updates from across the Cloud SDK.
A weekly digest of client library updates from across the Cloud SDK.
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".
]]>A weekly digest of client library updates from across the Cloud SDK.
Starting October 22, 2024, Monitoring Query Language (MQL) will no longer be a recommended query language for Cloud Monitoring, and we will begin to turn off certain usability features. For more information, see the deprecation note for MQL.
]]>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.
]]>Starting no sooner than January 7, 2025, Cloud Monitoring will begin charging for alerting. For information about the pricing model and examples of pricing scenarios, see Pricing for alerting.
]]>Log buckets in all regions supported by Cloud Logging can now be upgraded to use Log Analytics. For more information, see Supported regions.
Your dashboards will now recommend event types for display. For more information, see Show events on a dashboard.
]]>Agent-installation policies for the Ops Agent are now GA. For more information, see Overview of agent policies for the Ops Agent.
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.
Agent-installation policies for the Ops Agent are now GA. For more information, see Overview of agent policies for the Ops Agent.
]]>