Study guide

13.4 Diagnostics, Ops Agent, Managed Service for Prometheus & Audit Logs

Google Cloud Associate Cloud Engineer ACE

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction & Exam Overview

1.1 About the GCP Associate Cloud Engineer Exam 1.2 How to Use This Study Guide & Build a Study Plan

2 Chapter 2: Resource Hierarchy, IAM Basics & Cloud Identity

2.1 The GCP Resource Hierarchy: Organizations, Folders & Projects 2.2 Organization Policies & Granting IAM Roles 2.3 Cloud Identity: Managing Users and Groups

3 Chapter 3: APIs, Quotas & Billing Configuration

3.1 Enabling APIs and Provisioning Cloud Operations Suite 3.2 Assessing and Requesting Quota Increases 3.3 Billing Accounts, Project Linking & Billing Exports 3.4 Billing Budgets and Alerts

4 Chapter 4: Planning Compute & Storage Resources

4.1 Choosing the Right Compute Option: GCE vs. GKE vs. Cloud Run vs. Cloud Functions 4.2 Spot VMs, Custom Machine Types & Cost-Optimized Compute Planning 4.3 Choosing a Data Storage Product: Cloud SQL, BigQuery, Firestore, Spanner & Bigtable 4.4 Cloud Storage Classes & Persistent Disk Types

5 Chapter 5: Planning Network Resources

5.1 Load Balancing Options and Use Cases 5.2 Regional Resource Placement & High Availability Planning 5.3 Network Service Tiers: Premium vs. Standard

6 Chapter 6: Deploying Compute Engine Workloads

6.1 Launching Compute Engine Instances: Disks, SSH Keys & Availability Policies 6.2 Managed Instance Groups, Instance Templates & Autoscaling 6.3 OS Login and VM Manager for Fleet Configuration

7 Chapter 7: Deploying Google Kubernetes Engine Workloads

7.1 Installing and Configuring kubectl 7.2 Deploying GKE Clusters: Autopilot, Regional, Private & GKE Enterprise 7.3 Deploying Containerized Applications to GKE

8 Chapter 8: Deploying Serverless & Event-Driven Applications

8.1 Deploying Applications to Cloud Run and Cloud Functions 8.2 Event-Driven Architectures: Pub/Sub, Cloud Storage Triggers & Eventarc

9 Chapter 9: Deploying Data Solutions

9.1 Deploying Data Products: Cloud SQL, Firestore, Spanner, BigQuery & AlloyDB 9.2 Deploying Pub/Sub, Dataflow & Loading Data into Google Cloud

10 Chapter 10: Deploying Networking Resources & Infrastructure as Code

10.1 Creating VPCs, Subnets & Shared VPC 10.2 Firewall Rules, Cloud VPN & VPC Network Peering 10.3 Infrastructure as Code: Terraform, Config Connector, Cloud Foundation Toolkit & Helm

11 Chapter 11: Managing Compute Engine & GKE in Production

11.1 Connecting to and Managing Running Compute Engine Instances 11.2 Working with Snapshots and Custom Images 11.3 Managing GKE Clusters: Node Pools, Workloads & Artifact Registry Access 11.4 Horizontal and Vertical Pod Autoscaling in GKE

12 Chapter 12: Managing Cloud Run, Storage & Database Operations

12.1 Managing Cloud Run Revisions, Traffic Splitting & Scaling 12.2 Managing and Securing Cloud Storage Objects & Lifecycle Policies 12.3 Querying, Estimating Costs, Backup & Job Monitoring for Databases (Cloud SQL, BigQuery, Spanner, Dataflow)

13 Chapter 13: Networking Operations, Monitoring & Logging

13.1 Networking Operations: Subnets, Static IPs, Cloud DNS & Cloud NAT 13.2 Cloud Monitoring: Alerts, Custom Metrics & Dashboards 13.3 Cloud Logging: Buckets, Log Analytics, Routers & Filtering 13.4 Diagnostics, Ops Agent, Managed Service for Prometheus & Audit Logs

14 Chapter 14: IAM Policies & Role Types

14.1 IAM Policies: Structure, Bindings & Policy Hierarchy 14.2 IAM Role Types: Basic, Predefined & Custom Roles

15 Chapter 15: Service Accounts & Security Configuration

15.1 Creating Service Accounts & Assigning Least-Privilege Permissions 15.2 Assigning Service Accounts to Resources & Managing SA IAM Policies 15.3 Service Account Impersonation & Short-Lived Credentials

16 Chapter 16: Exam Readiness — Scenarios & Test-Day Strategy

16.1 Common ACE Exam Scenarios & Decision Frameworks 16.2 Test-Day Logistics, Time Management & Final Review Checklist

13.4 Diagnostics, Ops Agent, Managed Service for Prometheus & Audit Logs

Key Takeaways Explain This Topic AI

Cloud Monitoring, Cloud Logging, Error Reporting, Cloud Trace, and Cloud Profiler each answer a distinct diagnostic question; match the described symptom (metric anomaly, log entry, recurring exception, cross-service latency, CPU/memory hotspot) to the right tool.

status.cloud.google.com should be checked before assuming a widespread symptom across projects is a misconfiguration rather than a Google-side incident.

The Ops Agent replaces the older separate Monitoring and Logging agents on Compute Engine VMs, collecting metrics (including Prometheus scraping), logs, and process data through one YAML config, best deployed fleet-wide via an Ops Agent policy.

Managed Service for Prometheus runs on Monarch and supports PromQL across both Prometheus and native Cloud Monitoring metrics; use managed collection (Kubernetes operator) for GKE and self-deployed collection when full control is needed.

Data Access audit logs are off by default (except BigQuery) and are never retroactive — enabling them after an incident cannot recover missing access history, unlike the always-on Admin Activity, System Event, and Policy Denied logs.

Last updated: July 2026

Why This Topic Matters on the Exam

This section closes out Domain 4's monitoring-and-logging cluster with the remaining official bullets: using cloud diagnostics to research an application issue, checking Google Cloud's own status, deploying the Ops Agent, deploying Managed Service for Prometheus, and configuring audit logs. These are the "which tool do I reach for" questions — the exam wants you to know which of several overlapping-sounding tools applies to a described troubleshooting or configuration task.

Cloud Diagnostics: The Full Toolkit

When an application issue is reported, ACE expects you to know which observability tool answers which question, together forming what Google calls the Cloud Operations Suite (the modern name for the former "Stackdriver" umbrella):

Tool Answers

Cloud Monitoring Is a metric or uptime check outside its normal range right now?

Cloud Logging / Logs Explorer What specific log entries were written around the time of the issue?

Error Reporting Which exceptions/stack traces are recurring, and how often, automatically grouped across all instances?

Cloud Trace Where is latency being spent across a chain of microservice calls for one request?

Cloud Profiler Which functions in a running production service are consuming the most CPU or memory?

A realistic diagnostic workflow: an alert fires (Cloud Monitoring) → the engineer opens Logs Explorer to find matching error entries → Error Reporting shows the same exception has spiked across 40 instances in the last hour → Cloud Trace reveals the slow calls are all waiting on one downstream service → Cloud Profiler confirms that downstream service is CPU-bound on a specific function. Exam questions rarely require you to use all five in one scenario, but they do expect you to pick the one correct tool for a specific symptom (e.g., "recurring exceptions grouped automatically" → Error Reporting, not raw Logs Explorer).

Viewing Google Cloud Status

Before spending time debugging your own configuration, the exam expects you to know that status.cloud.google.com (the Google Cloud Status Dashboard) shows current and historical incidents, broken down by product and by region. A described scenario like "multiple teams across different projects report the same GKE control-plane symptom starting at the same time in the same region" is testing whether you'd check the status dashboard first , before assuming it's a misconfiguration in your own project.

Ops Agent

The Ops Agent is the modern, unified agent for Compute Engine VMs (and other environments, including on-premises and other clouds), replacing the older, separate Monitoring agent and Logging agent combination. Installing one Ops Agent per VM gets you:

Metrics — system metrics (CPU, memory, disk, network) plus application metrics, including scraping Prometheus-format exporters running on the VM.

Logs — application and system log collection, forwarded into Cloud Logging.

Process metrics — per-process resource usage.

Configuration is a single YAML file ( config.yaml ) defining receivers (where data comes from), processors (transformations), and pipelines (wiring receivers to destinations) — one pipeline structure for logging, one for metrics. Deployment options scale from a manual install, to a VM startup script , to an Ops Agent policy applied fleet-wide across many VMs at once (the preferred approach for managing dozens or hundreds of VMs consistently).

Managed Service for Prometheus

Google Cloud Managed Service for Prometheus is a fully managed, Prometheus-compatible metrics service built on Monarch , the same globally scalable backend that powers Cloud Monitoring. This means Prometheus-collected metrics and Cloud Monitoring's own ~6,500+ built-in metrics can be queried together with PromQL , across projects, without running and scaling your own Prometheus servers.

Two collection modes matter for the exam:

Managed collection — recommended for GKE : a Kubernetes operator automatically deploys, scales, and manages the collectors for you.

Self-deployed collection — you run the Managed Service for Prometheus binary yourself as a drop-in Prometheus replacement, useful when you need full control over the deployment (e.g., non-GKE compute) or are migrating an existing self-managed Prometheus setup.

The Ops Agent (on Compute Engine VMs) and the OpenTelemetry Collector (vendor-neutral, cross-cloud) are the two additional supported collection paths, rounding out four total ways to feed Managed Service for Prometheus.

Exam distinction: if a scenario describes "collecting Prometheus metrics from a GKE cluster with minimal operational overhead," the answer is managed collection via the Kubernetes operator — not manually deploying the Ops Agent (which targets Compute Engine VMs, not GKE Pods) and not standing up a self-managed Prometheus server.

Configuring Audit Logs

Audit logs were introduced from a security framing in Domain 5, but configuring them is itself an operational task tested here. Recall the four audit log types:

  • Type Default state Notes
  • Admin Activity Always on Cannot be disabled; API calls that change resource configuration/metadata
  • System Event Always on Cannot be disabled; Google-initiated changes not driven by a user

Policy Denied Always on Cannot be disabled (but exclusion filters can trim volume); access denials due to security policy

Data Access Off by default (except BigQuery, which is on by default) Must be explicitly enabled; can generate very high volume and additional charges

Configuring audit logs operationally means enabling Data Access logs where needed, via the IAM Audit Config — set at the organization, folder, or project level, or scoped to individual services, and further scoped by permission type ( ADMIN_READ , DATA_READ , DATA_WRITE ), with the option to exempt specific principals from generating entries.

Critical exam trap: Data Access logs are not retroactive . If a compliance investigation needs to know who read the contents of a specific Cloud Storage object last week, and Data Access logging was never enabled for Cloud Storage, that read history cannot be recovered after the fact — the audit config must have been turned on before the events occurred. This is one of the most commonly tested "gotcha" points connecting Domain 4's operational configuration to Domain 5's security requirements.

Section Takeaways

Cloud Monitoring, Logging, Error Reporting, Trace, and Profiler each answer a different diagnostic question — match the described symptom to the right tool.

Check status.cloud.google.com before assuming a widespread symptom is a misconfiguration in your own project.

The Ops Agent unifies metrics (including Prometheus scraping) and log collection on Compute Engine VMs in one agent, configured via a single YAML file, and is best deployed fleet-wide via an Ops Agent policy.

Managed Service for Prometheus runs on Monarch and supports PromQL across Prometheus and native Cloud Monitoring metrics; use managed collection for GKE and self-deployed collection when you need full control or are migrating existing Prometheus setups.

Admin Activity, System Event, and Policy Denied audit logs are always on; Data Access logs are opt-in (except BigQuery) and are never retroactive — enabling them after an incident cannot recover missing history.