No company dashboard yet, just alert emails and a few admin pages
Waiting on you Today we read health from Cloud Monitoring, alert emails and a handful of admin routes. Nothing shows active brands, hand-offs, activation or cost per brand. Proposed: a weekly partner view, a company view and a health view, all in v1. One staff page at /ops/weekly, reading our own tables, no third party tool. 11 Cloud Monitoring alert conditions
Your call Build the weekly views in the product or in an outside tool?
Read the full page
Data and analytics · 7.5
Dashboards Needs you Last checked 2026-10-26 Owner Param
Answer
No dashboard of company numbers exists; today we read health from Cloud Monitoring, alert emails and a few admin routes, and this page proposes three views, who reads each and when, once the events in the tracking plan exist.
Today
View
Shows
Who reads it
Source
Cloud Monitoring
Uptime of /, /healthz/ready, /api/config; 11 alert conditions
param@ and hello@ by email
brew/docs/production.md:112-115
App alerts
Vertex billing and quota, AI pause, treg low, 5xx rate, Sloosh down, once a day each
hello@
brew/alerts.js:1-13
GET /api/admin/visitorsWhich emails opened which brand, with access kind
Root admin
brew/server.js:657-666, 817-819 memory brew-access-rules
GET /api/admin/sessionsSign ins of one email; sign out everywhere
Root admin
brew/server.js:810-814
GET /api/admin/sourcesSource health for treg and Apify
Staff
brew/server.js:824 memory brew-apify-watch
brew-ops jobArata's connection states and table sizes
Whoever runs it
brew/db/status.mjs:16 memory brew-prod-backend
Brief status pill
Briefs sent to our team and where each stands
Staff
brew/brief-status.js:1-6
No view shows active brands, hand-offs, activation or cost per brand. handbook content/data-and-analytics/metric-definitions.md
Tomorrow
View
Shows
Reader
When
Version
Tag
Weekly partner view
Per partner: active, cards hearted, made, handed off, facts corrected, last sign in
Param, Sai, Arvind
Monday team call
v1
New, proposed
Weekly company view
North star, activation, return, taste, making, trust, cost per active brand
Param
Monday
v1
New, proposed
Health view
Uptime, errors, slow requests, connector reads failing, stale connections, spend against caps
Engineering
Daily
v1
New, proposed
Posting view
Posts approved, scheduled, published, failed
Team
Weekly
v2
New
Results view
Measured share, grade mix, results by family
Team and the brand's own view
Weekly
v3
New
Rules view
Runs, undos, spend inside limits
Team and the brand
Daily
v4
New
Proposed build
A staff only page in the product, /ops/weekly, reading the events, access_log and counters tables, no third party tool.
Numbers only as defined in metric definitions; every tile says its definition on hover.
Staff and demo activity filtered out by default.
How we do it
Every tile reads one defined number; a new tile means a new row in metric definitions first.
Until the page exists, Param reads the visitors list and the brief pill before the Monday call.
Run the ops job for table sizes and Arata's connections:
gcloud run jobs execute brew-ops --region=asia-south1 --wait
Numbers
Metric
Definition
Where measured
Status
Views live
Proposed views that exist
This page
0 of 3 for v1
Weekly view read
Mondays the view was opened before the call
access_log on /ops/weeklyProposed
Open
Build the weekly views in the product or in a tool? Proposal: a small staff page in the product, so data never leaves our database.Who owns the Monday read? Proposal: Sai prepares, Param decides.Show partners their own view? Proposal: not in v1; in v3 the brand gets its results view.
Sources brew/docs/production.md:112-115 brew/alerts.js:1-13 brew/server.js:657-666, 810-824 brew/brief-status.js:1-6 brew/db/status.mjs:16 memory brew-prod-backend, brew-access-rules, brew-apify-watch handbook content/data-and-analytics/metric-definitions.md, content/data-and-analytics/tracking-plan.md Source file content/data-and-analytics/dashboards.md · For agents: Markdown · JSON
