Docs › Google Cloud Scheduler monitoring with RunVouch
Google Cloud Scheduler monitoring with RunVouch
Google Cloud Scheduler monitoring beyond the status code: Cloud Scheduler counts an HTTP 2xx as success and retries on anything else. Everything that goes wrong inside a 2xx is yours to find.
How it runs on Google Cloud Scheduler
For a Cloud Run job, wrap the container command with rv run (the image needs Python 3). For an HTTP-triggered function, use the two HTTP calls or the Python client inside the handler.
Store the key
Reference the key from Secret Manager as an environment variable on the Cloud Run job or function (--set-secrets RUNVOUCH_KEY=runvouch-key:latest).
Wrap the job
# Cloud Run job, container command gcloud run jobs create nightly-report --image gcr.io/PROJECT/report \ --set-secrets RUNVOUCH_KEY=runvouch-key:latest \ --command rv --args run,nightly-report,--evidence-file,/tmp/report.html,--,python,report.py # schedule it gcloud scheduler jobs create http nightly-report --schedule "0 2 * * *" \ --uri "https://run.googleapis.com/v2/projects/PROJECT/locations/REGION/jobs/nightly-report:run" \ --oauth-service-account-email [email protected]
rv fails open: if RunVouch is unreachable the job still runs and you get one warning line.
Register the cadence and caps
rv agent nightly-report --cadence 24h --grace 30m --max-runtime 1h --evidence --cap-run-cost 2
Register the agent once, from anywhere with the key. Cadence is what turns a schedule that stopped into an alert; --evidence makes a run without evidence a failure; the caps pause the agent when it overspends.
What goes silent on Google Cloud Scheduler
- A paused scheduler job, or one whose service account lost
run.jobs.run, fails on the scheduler side; the alerting policy for that is not created by default. MISSED needs no policy. - A function that returns 200 after catching an exception is a success to Scheduler and to Cloud Monitoring.
- Scheduler retries plus function retries can run an agent several times an hour; the daily cost cap holds regardless.
What Google Cloud Scheduler does not tell you
Cloud Scheduler writes a log entry per attempt and a status per job in the console; it does not notify. A paused job, a job whose service account lost the invoke permission, or a job deleted with the project's Terraform state, disappears from the log without a line saying so. Cloud Monitoring alerting policies on scheduler.googleapis.com/job/attempt_count are possible but are not created by default.
What RunVouch detects
| Alert | What it means here |
|---|---|
| MISSED | cadence plus grace passed and no run started |
| FAILED | non-zero exit or a reported failure, with the stderr excerpt |
| NO_EVIDENCE | the run said ok but the file, URL or assertion you required is missing |
| STALLED | a run started and never ended within max runtime |
| RETRY_STORM | the same tool called with identical input many times in one run |
| BUDGET_RUN / BUDGET_DAY | cost cap crossed; the agent is paused until you resume it |
| DRIFT | duration or output size far off its 7-run baseline |
Set up in two minutes
- Get a free key (3 agents, no card) and store it where this page says.
- wrap the job: copy the snippet above into the scheduled job.
- Register the cadence once:
rv agent nightly-report --cadence 24h --grace 30m --evidence, or let the first run create the agent and set the cadence on the dashboard. - Send one test alert:
curl -X POST https://api.runvouch.com/v1/settings/test-alert -H "X-API-Key: $RUNVOUCH_KEY". The next missed, failed or empty run reaches the same channels.
Also running cloud functions?
Azure Functions timer trigger. Cloudflare Workers Cron Triggers. Vercel Cron Jobs. Supabase (pg_cron + Edge Functions). The full list of runtimes is on integrations, and the same agent can report from several of them: one job, one cadence, wherever it happens to run.
Need a key? Get a free key · Stuck? contact