Repository navigation
Conversation
…bservability digest to Slack The monitor had never seen a data proxy error: it queried the Worker as `data-source-coop`, but the Worker is `source-data-proxy`, so every run logged "Cloudflare: 0 errors". It also stopped altogether on 2026-10-10, when GitHub disabled the schedule after 60 days without repository activity. - The Cloudflare source now reads Workers Observability Issues, Cloudflare's own grouping of exceptions, 5xx responses and ERROR lines, rather than up to 500 raw ERROR events per window, which the proxy's ~800 ERROR lines per 6 hours would overflow. Vulnerability-scan detections are skipped, and so are groups first seen before `cloudflare_issues_since`, which are already tracked by hand. Issues carry a running total, so those errors are reported as "N times in total" and raise `total_count` to that total instead of adding to it. - `auto_fix` is off for data.source.coop: most proxy error groups are infrastructure (Cloudflare 52x, backend STS), not code a bot can fix. - New weekly digest (`src/digest.ts`, `digest.yml`, Mondays 16:00 UTC): gathers alert notifications and monitor definitions, Workers Issues, Analytics Engine traffic, error and latency figures, Workers Logs WARN/ERROR sources and the repo's open issues; has Claude write a short review; and posts it to Slack via `SLACK_WEBHOOK_URL`. It only suggests. A data source that fails is reported as unavailable rather than failing the digest. - Both scheduled workflows re-enable themselves on each run so the inactivity rule cannot switch them off again. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
sourcebot now watches the data proxy through Cloudflare's Workers Issues, and a new weekly digest reviews the proxy's observability and posts the review to #devops on Slack.
Why
The monitor had never seen a data proxy error.
config.yamlnamed the Workerdata-source-coop, but it issource-data-proxy, so every run loggedCloudflare: 0 errorswhile Vercel errors came through normally. The monitor also stopped altogether on 2026-10-10: GitHub disabled its schedule (disabled_inactivity) after 60 days without repository activity.Monitor
/workers/observability/issues), Cloudflare's own grouping of exceptions, 5xx responses and ERROR lines. The old source read up to 500 raw ERROR events per 6-hour window, and the proxy logs about 800 in that time, mostly one known error (data.source.coop#206), so it would have been cut off.cloudflare_issues_since(2026-11-19). The roughly 20 groups that already exist are tracked by hand (#206, #280, #281), so the first run won't file duplicates.total_countis raised to that total rather than added to (MAX(total_count + ?, ?)). Vercel errors keep their per-window counts.auto_fixis now off for data.source.coop. Most proxy error groups are infrastructure problems (Cloudflare 520/524/525 errors, backend STS failures), not code a bot can fix. A person can still assign Scooter to an issue.Digest
src/digest.tsruns from.github/workflows/digest.ymlon Mondays at 16:00 UTC, or manually withdaysand aposttoggle.data-proxy:monitor definitions and their alert notifications, one per notification (the webhook copy, not the duplicate email);anthropic_modelsetting, one turn, no tools) writes a Slack message of at most about 2,500 characters: which alerts were real, what drove errors and latency, which noise sources an open issue tracks and which are untracked, and up to 5 suggested actions. It only suggests: it files no issues and changes no monitors.SLACK_WEBHOOK_URLsecret. Without it, the digest prints to the workflow log.Keepalive
Both scheduled workflows run
gh workflow enableon themselves at the end of each run (actions: write), so the inactivity rule shouldn't switch them off again. GitHub doesn't document whether re-enabling an enabled workflow resets the 60-day clock, so check after about two months.Before merging
SLACK_WEBHOOK_URL, a #devops incoming webhook.CLOUDFLARE_API_TOKENtoken. The digest needs it for alert policies and history; without it, that section reports unavailable.After merging
gh workflow enable monitor.yml -R source-cooperative/sourcebot.postunchecked, and read the output in the log before the first Monday post.Testing
npx tsc --noEmitpasses andnpx vitest runpasses (40 tests). New tests cover:Neither job has been run against the live Cloudflare APIs in this branch. The Workers Issues response fields (
title,type,count,firstObserved,lastObserved) and every query were checked against production by hand this week, but the manual digest run above is the first full end-to-end run.🤖 Generated with Claude Code