Stay organized with collections Save and categorize content based on your preferences.
The Ops Agent is now Generally Available. The GA version incorporates fixes and improvements based on the feedback from Preview users. This guide provides migration steps for the following users:
Ops Agent Preview users to migrate to the GA version of the agent.
Users of the legacy Logging and Monitoring agents to migrate to the Ops Agent.
To install the latest version of the Ops Agent, complete the Upgrading the agent procedures.
If you edited the agent's default configuration to remove the default_pipeline, add the following snippet to the agent configuration to keep that pipeline disabled:
logging:
service:
pipelines:
default_pipeline:
receivers: []
exporters: []
metrics:
service:
pipelines:
default_pipeline:
receivers: []
exporters: []
The following table lists the commands for managing the agent that changed for the GA release:
Procedure GA version Preview version Starting the agentsudo service google-cloud-ops-agent start N/A Stopping the agent sudo service google-cloud-ops-agent stop N/A Restarting the agent sudo service google-cloud-ops-agent restart sudo systemctl restart google-cloud-ops-agent.target Checking agent status sudo service google-cloud-ops-agent status sudo systemctl status google-cloud-ops-agent.target Migrating from the legacy agents to the Ops Agent
To migrate from the legacy Logging and Monitoring agents, complete the following steps.
Uninstall the Logging and the Monitoring agents.
After you uninstall the agent, the Google Cloud console might take up to one hour to report this change.
Install the latest version of the Ops Agent on a single virtual machine.
You also have the option of installing and managing the Ops Agent on multiple VMs.
Configure the Ops Agent as needed.
The following table describes differences in the data ingested by the Ops Agent and the Monitoring agent.
Metric type, omittingagent.googleapis.com Ops Agent (GA)† Ops Agent (Preview)† Monitoring agent cpu_state The possible values for Windows are idle, interrupt,
system and user. The possible values for Windows are idle, interrupt,
system and user. The possible values for Windows are idle and used. disk/bytes_used and
disk/percent_used Ingested with the full path in the device label; for example, /dev/sda15.
Not ingested for virtual devices like tmpfs and udev.
/dev in the path in the device label; for example, sda15.
Ingested for virtual devices like tmpfs and udev.
/dev in the path in the device label; for example, sda15.
Ingested for virtual devices like tmpfs and udev.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-11 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-11 UTC."],[],[]]
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4