A weekly digest of client library updates from across the Cloud SDK.
The Dashboards page of the Cloud Console has been refreshed. For more information about dashboards, see the following documents:
]]>You can now use a variable to control the visibility of a dashboard widget. For more information, see the following documents:
]]>You can now create and manage your log views by using the Google Cloud console. For more information, see Configure log views on a log bucket.
]]>When you create a snooze from the Incident details page, you can now apply the snooze to other incidents that have one or more of the same resource labels. For more information, see Create a snooze.
]]>A weekly digest of client library updates from across the Cloud SDK.
You can now create custom organization policies on alerting policies, notification channels, and snoozes. For more information, see Use custom organization policies.
]]>You can now monitor usage, throughput, and latency, and troubleshoot 429 errors on Vertex AI foundation models like Google Gemini and Anthropic Claude by using a new predefined dashboard. After querying a model from the Vertex AI Model Garden, you can find the models associated with your project from the Vertex AI Dashboard page under the "Model observability" heading.
To customize the dashboard and explore relevant metrics in Cloud Monitoring, click Show All Metrics. For information about using dashboards in Cloud Monitoring, see View and customize Google Cloud dashboards.
]]>The Trace Explorer page in the Google Cloud console has been refreshed. The new page aggregates and displays information about spans using visualizations like heatmaps. You can use menus to apply filters and to group traces by span and service name. You can also explore individual traces and share traces. For more information, see the following documents:
Introducing trace scopes. Trace scopes are persistent, project-level resources that the Trace Explorer page uses to determine which projects to search for trace data. You can create, edit, and delete trace scopes. You can also set one trace scope as the default trace scope, which determines the projects that the Trace Explorer searches when the page is opened.
For more information, see the following documents:
]]>On April 22, 2025, Cloud Logging will replace the single, global quota for the number of calls to write log entries with a set of volume-based regional quotas. For more information, see Logging API quotas and limits.
]]>A weekly digest of client library updates from across the Cloud SDK.
You can now create analytics views, which let you transform your log data into a custom format. You can then use SQL to query your analytics views. This feature is in Public Preview. For more information, see the following documents:
]]>A weekly digest of client library updates from across the Cloud SDK.
Cloud Logging adds support for the northamerica-south1 region. For a complete list of supported regions, see Supported regions.
You can now create custom roles that let you create and manage Log Scopes. Log Scopes are in Public Preview. For more information, see Create and manage log scopes: Before you begin.
]]>A weekly digest of client library updates from across the Cloud SDK.
Reporting of the "pending" status of the Ops Agent on the Cloud Monitoring VM Instances dashboard has been refined to include additional states. For more information, see Use VM Instances dashboard.
Reporting of the "pending" status of the Ops Agent on the Cloud Monitoring VM Instances dashboard has been refined to include additional states. For more information, see Use VM Instances dashboard.
]]>You can now override the validation that checks for metric existence when you create a PromQL-based alerting policy. For more information, see Disable check for metric existence.
Text widgets can now link to sections of a dashboard and they can render variables. For more information, see the following documents:
]]>Editing Log Analytics charts that are saved to a dashboard directly in the Dashboards page is now generally available (GA).
]]>A weekly digest of client library updates from across the Cloud SDK.
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.
]]>