For organizations, folders, and projects, you can now configure default settings for observability buckets. Default settings let you specify the following for new observability buckets:
This feature is in public preview. To learn more, see Set defaults for observability buckets.
You can now configure observability buckets to be in the following locations:
Your trace data is stored in an observability bucket. To learn more, see Trace storage overview.
]]>Starting February 18, 2026, trace sinks are deprecated. For more information, see Export trace spans with sinks deprecation.
You can use the Log Analytics page, which provides a SQL query interface, to query both your trace and log data. To learn more, see the following documents:
To migrate to using Log Analytics page from a sink-based export of trace data to BigQuery, see Migrate to Log Analytics.
To query your trace data by using the Log Analytics page, see Query and analyze traces.
To query your trace data by using BigQuery services, see Query a linked BigQuery dataset.
You no longer need to configure BigQuery reservation assignments to create SQL-based alerting policies or run Log Analytics queries on BigQuery slots. These queries now use on-demand slots by default if no BigQuery reservation assignment exists.
For more information, see the following documents:
]]>You can use the Cloud Logging API MCP server to let agents and AI applications interact with your log entries. This feature is in Preview.
]]>You can use the Cloud Monitoring API MCP server to let agents and AI applications interact with your time series data. This feature is in Preview.
You can now ingest OTLP metrics into Cloud Monitoring by using an OpenTelemetry Collector, an OTLP exporter, and the Telemetry API. For more information, see OTLP metric ingestion overview. The Telemetry API for metric ingestion is in Preview.
]]>You can now analyze your trace data by using the Log Analytics page in the Google Cloud console. This page supports SQL queries and lets you view your query results as a table or as a chart. Your SQL queries can also join your trace and log data. This feature is in Public Preview.
To learn more about analyzing and viewing trace data, see the following documents:
Cloud Trace now stores your trace data in an observability dataset. You can continue to view your trace data by using the Trace Explorer page. If you create a link on your dataset, then you can use services like BigQuery to query and analyze your trace data. To learn more, see the following documents:
]]>You can now export your Crashlytics data and (optionally) Firebase sessions data to Cloud Logging. Once the data is exported, it's also available to Cloud Monitoring, so you can filter your logs, build custom dashboards, set up custom alerts, and even export the data to other services. For information about how to export your Crashlytics data, see Export Crashlytics data to Cloud Logging, and for information about how you can use this data, see What can you do with Crashlytics data in Cloud Logging.
]]>To support correlation between log and trace data, the following changes have been made:
The required format for the LogEntry.trace field has been relaxed. The
preferred format for this field is the trace ID. However, you can continue
to provide the full resource name. For more information, see
LogEntry.
If you open the Trace Details flyout page by using options provided in a log entry, then the resources listed in the default trace scope are searched for the trace data.
If you open the Logs Explorer page by using options on span data, then the resources listed in the default log scope are searched for log data.
To learn more about default scopes, see Configure observability scopes for multi-project queries.
You can now install and manage the Ops Agent on virtual machines across zones in your Google Cloud project by using global VM Extension Manager extension policies. Global and zonal extension policies can keep the installed version of the agent current, keep a specified version of the agent installed, and other tasks. For more information, see Install and manage the Ops Agent by using VM Extension Manager policies.
You can now install and manage the Ops Agent on virtual machines across zones in your Google Cloud project by using global VM Extension Manager extension policies. Global and zonal extension policies can keep the installed version of the agent current, keep a specified version of the agent installed, and other tasks. For more information, see Install and manage the Ops Agent by using VM Extension Manager policies.
To support correlation between log and trace data, the following changes have been made:
The required format for the LogEntry.trace field has been relaxed. The
preferred format for this field is the trace ID. However, you can continue
to provide the full resource name. For more information, see
LogEntry.
If you open the Trace Details flyout page by using options provided in a log entry, then the resources listed in the default trace scope are searched for the trace data.
If you open the Logs Explorer page by using options on span data, then the resources listed in the default log scope are searched for log data.
To learn more about default scopes, see Configure observability scopes for multi-project queries.
]]>Your Application Monitoring dashboards now display the trace spans that are associated with your registered App Hub applications. The display includes annotations that let you identify services and workloads. You can also open the Trace Explorer page from your Application Monitoring dashboards. To learn more, see the following documents:
Cloud Logging adds support for the asia-southeast3 region. For a complete
list of supported regions, see
Supported regions.
You can now collect, view, and analyze multimodal prompts and responses from your agentic applications that use the LangGraph or Agent Development Kit (ADK) frameworks. This feature is in Public Preview.
To learn more, see the following documents:
]]>java.time methods (#1729) (323eb33)On December 15, 2025, it was announced that your Application Monitoring dashboards will display the trace spans that are associated with your registered App Hub applications. Those dashboards don't display trace data. To view your trace data, use the Trace Explorer page.
]]>Your Application Monitoring dashboards now display the trace spans that are associated with your registered App Hub applications. The display includes annotations that let you identify services and workloads. You can also open the Trace Explorer page from your Application Monitoring dashboards. To learn more, see the following documents:
The Trace Explorer has been updated to include annotations that let you identify App Hub-registered services and workloads. The link provided with a service or workload lets you open the corresponding Application Monitoring dashboard. To learn more, see the following documents:
The default setting for the time-range selector for the Logs Explorer is now five minutes. The previous default was one hour.
]]>You can now add a widget to a dashboard that lets you manage the settings for a variable. To learn more, see the following documents:
The Google Cloud CLI (gcloud) commands to manage
Cloud Monitoring alerting policies are now generally available.
For more information, see gcloud monitoring
policies.
You can now install and manage the Ops Agent on virtual machines in a specified zone by using VM Extension Manager extension policies. You can use extension policies to keep the installed version of the agent current, keep a specified version of the agent installed, and other tasks. For more information, see Install and manage the Ops Agent by using VM Extension Manager policies.
You can now install and manage the Ops Agent on virtual machines in a specified zone by using VM Extension Manager extension policies. You can use extension policies to keep the installed version of the agent current, keep a specified version of the agent installed, and other tasks. For more information, see Install and manage the Ops Agent by using VM Extension Manager policies.
]]>You can now collect, view, and analyze prompts and responses from your agentic applications when they are built with the Agent Development Kit (ADK). This feature is in Public Preview.
Collect and view multimodal prompts and responses describes how to do the following:
You can now view the topology for applications that you register with App Hub. The topology map provides a graphical view of the relationships between the services and workloads in your App Hub application. The topology map also displays alerts and traffic latency, which can help you understand how your application is performing and diagnose issues. This feature is in Public Preview.
To learn more, see the following:
]]>You can now use the Google Cloud CLI and the Cloud Monitoring API to list incidents and get incident details. This feature is in Public Preview. For more information, see the following pages:
]]>The query builder in the Log Analytics page is generally available (GA). For more information, see Build, edit, and run a query.
]]>Application Monitoring is now generally available (GA). Application Monitoring lets you monitor the resources and infrastructure from the perspective of an App Hub application. The out-of-the-box dashboards that Application Monitoring creates can help you understand how your application's resources are performing, and they can help you diagnose issues.
Cloud Logging has removed the quota for write requests per minute, which has been replaced by volume-based regional quotas. We've also removed the references to August dates for the removal of the old quota from the public documentation. For more information, see Logging API quotas and limits.
]]>When viewing a chart, you can now open a flyout that displays the chart and related log entries. To explore your metric and log data in more detail, you can then use the toolbars and menus in the flyout. To learn more, see the following:
]]>