LocalCloud Cloud Monitoring Local Emulator
Get started
local.cloud — Cloud Monitoring Local Emulator .md Open tab
LocalCloud Google Cloud in-a-box

Cloud Monitoring

Cloud Monitoring stores time-series metrics and supports observability for applications and infrastructure. LocalCloud provides documented metric writes, queries, and configuration metadata.

When to use Cloud Monitoring

Typical uses

Use when application health is expressed as numeric measurements over time, with labels identifying resources or components. Test metric ingestion and time-window queries with deterministic points.

Examples

  • Custom application metrics
  • Metric and alert-configuration tests
Operations

Explore another service

View all
Local workflow

Example usage

Install the CLI, start LocalCloud, and export its environment in the same shell. Generated endpoints account for remapped ports.

1. Install and start · shell
curl -fsSL https://local.cloud/install.sh | sh
localcloud start --local-only
# Export GOOGLE_CLOUD_PROJECT and CLOUD_MONITORING_EMULATOR_HOST
eval "$(localcloud env)"

Write and query a custom metric

  1. Create a metric descriptor for completed requests.
  2. Write timestamped points with consistent labels.
  3. Query the time interval and verify the returned values.

Documented workflows

  • Time-series and metric-descriptor create/list APIs
  • Notification-channel metadata
  • Alert-policy create/get/list/update/delete APIs

Service boundaries

  • Limited query alignment/aggregation
  • Validate alert evaluation, notifications, uptime execution, and dashboards in Google Cloud
Try it in your project

Code examples and integrations

Start with the local guides. Official Google Cloud samples may need endpoint changes and can cover features outside the workflows listed here.

Integration

Build an integration test loop

Start the runtime, verify readiness, exercise your SDK, and clean up test state.

Open guide
Agent testing

Use Cloud Monitoring with an AI agent

Before the agent changes application logic, have it create local Cloud Monitoring state, read it back with the project SDK, and note which feature the check covered. That first local call catches accidental production routing and needs no GCP account, service-account key, or billing project.

Configure this repo

Set up this repository to use LocalCloud for local GCP development. First read https://local.cloud/ai/agents.md, then inspect this repo, identify the GCP services and SDK language, configure emulator environment variables, and run the narrowest integration test against localhost. Do not use real GCP credentials or production endpoints.

Production endpoints, auth, IAM, quotas, regional behavior, and final release validation still need the target Google Cloud project.

Agent resources has more prompts and the AGENTS.md template.

Related guides

Desktop view