The Ops Agent is the primary agent for collecting telemetry from your Compute Engine instances. Combining logging, metrics, and traces into a single agent, the Ops Agent uses Fluent Bit for logs, which supports high-throughput logging, and the OpenTelemetry Collector for metrics and traces.
To install the Ops Agent, see Installing the Ops Agent.
Ops Agent featuresOverall features include:
- Single download and installation/upgrade process.
- Simple, unified, YAML-based configuration.
- Support for standard Linux and Windows distros.
- Proxy support.
Logging features include:
Improved performance compared to the legacy Logging Agent:
- High throughput capability, taking full advantage of multi-core architecture.
- Efficient resource (e.g. memory, CPU) management.
Collecting logs from various sources:
- Standard system logs (
/var/log/messagesfor Linux, Windows Event Log) collected with no configuration.
- File-based logs with customizable paths and refresh interval.
- Journald daemon / systemd logs.
- Logs over TCP protocol.
- Logs over Forward protocol (used by Fluent Bit and Fluentd).
- Standard system logs (
Third-party application support
- Curated third-party application log integration that recognizes common app log file paths and formats.
Monitoring features include:
- System metrics collected with no configuration. Metrics collected include:
- Third-party application support
- Curated integrations for third-party application metrics, which collect common app metrics and offer sample dashboards and alert policies.
- Collection of Prometheus metrics from applications running on Compute Engine.
- Collection of OpenTelemetry Protocol (OTLP) metrics and traces from applications instrumented with OpenTelemetry SDKs.
- Collection of NVIDIA Data Center GPU Manager (DCGM) metrics.
The Cloud Monitoring Metrics Management page provides information that can help you control the amount you spend on chargeable metrics without affecting observability. The Metrics Management page reports the following information:
- Ingestion volumes for both byte- and sample-based billing, across metric domains and for individual metrics.
- Data about labels and cardinality of metrics.
- Use of metrics in alerting policies and custom dashboards.
- Rate of metric-write errors.
Trace features include:
- Collection of OpenTelemetry Protocol (OTLP) traces from applications instrumented with OpenTelemetry SDKs.
Virtual machine instances
The following types of VM instances belong to managed services that implement service-specific Monitoring support. Don't try to manually install or configure the Ops Agent on them:
- App Engine standard has built-in Monitoring support. Agents aren't needed.
- App Engine flexible environment instances have pre-installed agents with service-specific configurations.
- Dataflow instances have pre-installed legacy Monitoring agents with service-specific configurations.
- Dataproc instances have pre-installed legacy Monitoring agents with service-specific configurations.
- Google Kubernetes Engine node instances:
- GKE on Google Cloud instances have Cloud Operations for GKE pre-installed. Cloud Operations for GKE is an integrated monitoring and logging solution that is enabled by default for new container clusters and can be enabled for existing container clusters. For information, see Configuring Cloud Operations for GKE.
- Anthos clusters on VMware instances have an integrated logging and monitoring solution that collects status about system components. For information, see Logging and monitoring.
The Ops Agent supports the following operating systems on compatible VM instances. For information about Arm VM instances, see Support for Compute Engine Arm VMs.
Linux operating systems
The agent supports the following Linux operating systems:
- CentOS 7
- Rocky Linux 8
- Rocky Linux 9
- RHEL 7: rhel-7, rhel-7-9-sap-ha
- RHEL 8: rhel-8, rhel-8-1-sap-ha, rhel-8-2-sap-ha, rhel-8-4-sap-ha
- RHEL 9: rhel-9
- Debian 10 (Buster)
- Debian 11 (Bullseye)
- Debian 12 (Bookworm)
- Ubuntu 20.04 LTS (Focal Fossa): ubuntu-2004-lts, ubuntu-minimal-2004-lts
- Ubuntu 22.04 LTS (Jammy Jellyfish): ubuntu-2204-lts, ubuntu-minimal-2204-lts
- Ubuntu 23.04 (Lunar Lobster): ubuntu-2304-amd64, ubuntu-minimal-2304-amd64
- SLES 12: sles-12, sles-12-sp3-sap, sles-12-sp4-sap, sles-12-sp5-sap
- SLES 15: sles-15, sles-15-sp1-sap, sles-15-sp2-sap, sles-15-sp3-sap, sles-15-sp4-sap
- OpenSUSE Leap 15: opensuse-leap (opensuse-leap-15-3-*, opensuse-leap-15-4-*)
Support for Compute Engine Arm VMs
The Ops Agent supports Compute Engine Tau T2A Arm VM instances. The Ops Agent is supported for Arm VMs on the following OS images:
- Debian 11 (Bullseye): Ops Agent version 2.36.0
- Ubuntu 20.04 LTS (Focal Fossa): Ops Agent version 2.39.0
- RHEL 9: Ops Agent version 2.40.0
- Rocky Linux 9: Ops Agent version 2.40.0
The Ops Agent is supported on a subset of the images supported by Compute Engine. For more information about Compute Engine Arm VMs, see Creating and starting an Arm VM instance.
Windows operating systems
The agent supports the following Windows operating systems:
- Windows Server: windows-2012-r2, windows-2016, windows-2019, windows-2022
- Windows Server Core: windows-2012-r2-core, windows-2016-core, windows-2019-core, windows-20h2-core, windows-2022-core
Agent access requirements
Installing the agent requires access to the following DNS names:
Google Cloud package repository:
Google downloads subdomain:
Running the agent requires access to the following DNS names:
OAuth2 token server:
Older versions of the agent may require access to
If you're using an older version of the agent, it's recommended that you upgrade your agent to the latest version.
The agent uses TCP ports within the VM for inter-process communication. The following ports, which do not need to be open externally, must be available to the agent on your VM:
The Ops Agent is subject to the Agents deprecation policy.
For deprecation information for legacy features and versions, refer to Google Cloud's operations suite deprecations.
PricingIf you install the Ops Agent, then you might be charged for the metrics, logs, or traces that the agent sends to your Google Cloud project. For pricing information, see the following documents:
To collect OpenTelemetry Protocol (OTLP) traces, you must configure the agent to collect traces from an instrumented application; for more information, see Collect (OTLP) traces with the Ops Agent.
- To install the Ops Agent, see Installing the Ops Agent.