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
Get startedWhat 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
- Scheduler: locally minted OAuth and OIDC tokens for HTTP targets (#1243)
- Scheduler: App Engine targets, delivered to a local stand-in named with
--appengine-url(#1447) - Logging: tailing, exclusions, buckets, views and log-based metric configuration
- Logging: sinks delivered to Cloud Storage, Pub/Sub, BigQuery and another project, and intercepting sinks (#1404, #1451, #1521)
In the console
What's verified
Follow the operation matrix to see what the backend serves and the tests linked to Verified calls.
Not supported
- 01 / Local boundary
Scheduler's OIDC and OAuth tokens are local fixtures and grant no Google Cloud access.
- 02 / Local boundary
Logging: in memory in every mode, bounded at 20,000 entries
- 03 / Local boundary
Log-based metrics are stored; they do not produce Cloud Monitoring time series.
Source: docs/compatibility.md at main 0ea2594.
Questions
Does Cloud Logging keep entries across a restart?
Build against Google Cloud APIs, locally
Free and open source under Apache-2.0. No account, no sign-up, no Google Cloud bill.