Legacy Monitoring and Logging agents end of support

Important: This deprecation applies only to environments where you installed the legacy Monitoring agent or the legacy Logging agent, not to managed environments with built-in or pre-installed monitoring and logging agents.

Google Cloud Observability is phasing out the legacy Monitoring and Logging agents.

As of September 28, 2026, all standard maintenance and regular bug fixes for the agents officially end, initiating a 12-month migration grace period. During this time, Cloud Customer Care will assist with your migration efforts via support tickets. Migration support ends on September 28, 2027, after which all migration efforts must be managed independently.

Migration options

We recommend migrating to one of the following supported alternatives as soon as possible:

• Ops Agent: The primary and preferred agent for collecting telemetry from your Compute Engine instances. This agent combines logging and metrics into a single agent, providing YAML-based configurations for collecting your logs and metrics, and features high-throughput logging. For more information, see Migrating from the legacy agents to the Ops Agent.
• Google-Built OpenTelemetry Collector: Google's production-ready build of the open-source OpenTelemetry Collector. It lets you send correlated OpenTelemetry Protocol (OTLP) traces, metrics, and logs to Google Cloud Observability and other backends from applications. For more information, see Overview of the Google-Built OpenTelemetry Collector.
• Upstream Fluentd (logging only): The open-source, community-driven log data collector that the legacy Logging agent was built upon. Many legacy environments use highly customized Fluentd configurations that can't be translated for the Ops Agent. By pairing upstream Fluentd with the Google-platform plugins, you can maintain your current setups and make sure your logs continue to flow into Cloud Logging without interruption. For more information, see Migrate from the legacy Logging agent to upstream Fluentd.

Identify affected Compute Engine instances

To identify Compute Engine instances running the legacy Monitoring agent or the legacy Logging agent, follow these steps:

1. In the Google Cloud console, go to the  Metrics explorer page:

   Go to Metrics explorer

   If you use the search bar to find this page, then select the result whose subheading is Monitoring.

2. In the toolbar of the query-builder pane, select the button whose name is  PromQL.
3. In the Results pane, select the Table.
4. Enter one of the following queries into the editor, and then click Run query:
   • To generate a table that lists the instance of ID each VM running an agent, along with the version of the agent, use:

     max by (instance_id, version, ${__groupby}) ({__name__="agent.googleapis.com/agent/uptime", monitored_resource="gce_instance"})
             

   • To generate a table that shows the total number of instances running each agent version, use:

     count by (version, ${__groupby}) ({__name__="agent.googleapis.com/agent/uptime", monitored_resource="gce_instance"})
             

   In the version column, entries showing stackdriver_agent refer to the legacy Monitoring agent, while entries showing google-fluentd refer to the legacy Logging agent.