Opt-in: --services scheduler,logging

Cloud Scheduler and Cloud Logging, built in.

Cron jobs to HTTP and Pub/Sub targets, and log write and read with a filter subset.

Backed by: CloudBurrow CloudBurrow

In the console

Cloud Scheduler jobs with their schedules and targets — Captured 2026-09-28 from main @5da2bd0. Product icons hidden.

A Cloud Scheduler job, its target and its last run — Captured 2026-09-28 from main @5da2bd0. Product icons hidden.

The live Logs Explorer, streaming from the local stack — Captured 2026-09-28 from main @5da2bd0. Product icons hidden.

What it covers

Cloud Scheduler and Cloud Logging are built by CloudBurrow, because Google publishes no emulator for either, and each starts with --services. Scheduler fires cron jobs at HTTP and Pub/Sub targets. Logging writes and reads entries, which also appear in the console’s Logs Explorer.

Scheduler: cron schedules in IANA time zones
Scheduler: HTTP and Pub/Sub targets, with retries
Logging: write and read, with a documented filter subset
Logging: entries appear in the console's Logs Explorer

What's verified

Cloud Scheduler

7 of 8 RPCs Verified in v0.1.0

8 of 8 RPCs Verified on main next release

Every Cloud Scheduler RPC, with its test →

Cloud Logging (write and read)

3 of 6 RPCs Verified in v0.1.0

4 of 6 RPCs Verified on main next release

Every Cloud Logging (write and read) RPC, with its test →

Not supported

Scheduler: no App Engine targets and no OIDC or OAuth tokens
Logging: in memory in every mode, bounded at 20,000 entries
Logging: no sinks, log-based metrics or tailing

Source: docs/compatibility.md at main 82a2eb9.

Questions

Does Cloud Logging keep entries across a restart?

No. It is in memory in every mode and bounded at 20,000 entries; the oldest go first.

Link to this answer

Build against Google Cloud APIs, locally

Free and open source under Apache-2.0. No account, no sign-up, no Google Cloud bill.

Get started View on GitHub