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

Cloud Logging

Cloud Logging collects and queries structured application logs. It helps developers investigate requests, errors, and resource activity.

When to use Cloud Logging

Typical uses

Use when you need searchable records of individual application events, including severity, structured fields, and request IDs for investigating failures.

Examples

  • Application log ingestion
  • Request tracing and audit inspection
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_LOGGING_EMULATOR_HOST
eval "$(localcloud env)"

Find a failed request in structured logs

  1. Write log entries containing severity and a request ID.
  2. Query with a supported filter.
  3. Check that the expected entry and fields are returned.

Documented workflows

  • Log ingestion, listing, and local filtering
  • Sink configuration and runtime/KMS audit events
  • Logs-based metric definition create/get/list/update/delete APIs

Service boundaries

  • Limited Google filter semantics
  • Metric definitions do not derive values from log entries
  • Validate log-based metrics, exclusions, and sink delivery 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 Logging with an AI agent

Before the agent changes application logic, have it create local Cloud Logging 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