ReleaseBytes
gcp Google Cloud release notes ·

Cloud Trace Adds Bucket Management and Automatic Span Generation for MCP Servers

observabilitygcpgaengineer
feature

Cloud Trace now allows users to update existing observability bucket metadata, including display name, description, and Cloud KMS key. This update also introduces the ability to manually create observability buckets before receiving trace data, offering more control over storage location and encryption. Additionally, remote MCP servers like Policy Troubleshooter and Managed Service for Apache Airflow will automatically generate trace spans for tools/call operations. These enhancements provide greater flexibility in managing trace data and improve visibility into agentic application behavior for Cloud Trace users.

Features (3) ›
  • Cloud Trace

    You can update the display name, description, and Cloud KMS key applied to a _Trace observability bucket. For more information, see Update observability buckets .

    Update observability buckets
  • Cloud Trace

    You can manually create the _Trace observability bucket before your project receives trace data. When creating the bucket, you must specify a storage location. Google Cloud Observability applies the Cloud KMS key defined in your default settings unless you explicitly specify a different key in your create request. For more information, see the following documents: Create observability buckets Set defaults for observability buckets

    Create observability bucketsSet defaults for observability buckets
  • Cloud Trace

    The following remote MCP servers automatically generate a trace span for tools/call operations. Policy Troubleshooter Managed Service for Apache Airflow These spans can help you understand the behavior of your agentic applications. For more information, see Investigate MCP calls using Trace .

    Investigate MCP calls using Trace
Read the original announcement →

https://docs.cloud.google.com/release-notes#August_24_2026

Related releases