Skip to content

Commit a10bf61

Browse files
committed
docs: update infra dashboard plan with Phase 1 completion status
Note search-console-ingest workflow failures (5+ days) as follow-up item.
1 parent 21a911b commit a10bf61

1 file changed

Lines changed: 10 additions & 3 deletions

File tree

docs/plans/infra-dashboard-and-alerts.md

Lines changed: 10 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,14 +4,21 @@
44
55
## Implementation Status
66

7-
- [x] **Phase 1 (partial)**: D1 schema, infra-collector worker, `/api/infra-dashboard` API, dashboard UI with tabs (SEO/Infrastructure/Workflows/Security), CACHE_KV binding fix
8-
- [ ] **Phase 1 (remaining)**: Deploy infra-collector, apply schema to D1, create CF Analytics token, test end-to-end
9-
- [ ] **Phase 2**: Workflow health monitoring (REST API queries in collector)
7+
- [x] **Phase 1**: D1 schema, infra-collector worker, `/api/infra-dashboard` API, dashboard UI with tabs (SEO/Infrastructure/Workflows/Security), CACHE_KV binding fix. Deployed and collecting data (2026-03-28).
8+
- [x] Deploy infra-collector, apply schema to D1, create CF Analytics token
9+
- [x] Worker metrics filtered to site-relevant workers only (shared account)
10+
- [x] Tab state persisted in URL params (`?tab=infra&days=7`)
11+
- [x] Full worker names shown in Worker Performance table
12+
- [ ] **Phase 2**: Workflow health monitoring enhancements
1013
- [ ] **Phase 3**: Alert & report system (tiered routing, email delivery)
1114
- [ ] **Phase 4**: Deploy/CI monitoring
1215
- [ ] **Phase 5**: Cloudflare Data Platform (Pipelines + R2 SQL)
1316
- [ ] **Phase 6**: Client portal (multi-tenant)
1417

18+
## Follow-Up Items
19+
20+
- [ ] **Investigate search-console-ingest workflow failures** — Last 5+ days of runs show `status: errored` (2026-03-24 through 2026-03-28). Error message is null in the Workflows list API; need to check individual instance logs via CF dashboard or the instance detail endpoint (`GET /accounts/{id}/workflows/{name}/instances/{instance_id}`). This is a pre-existing issue surfaced by the new dashboard, not caused by it.
21+
1522
## Problem
1623

1724
The current `/dash` route is SEO-only: search performance, content gaps, content quality, and security assessment. Clients can see how their content ranks but have no visibility into:

0 commit comments

Comments
 (0)