A product analytics style metrics dashboard page says a nightly media pipeline produced 18,420 searchable articles when 18,487 were eligible. The Node.js server-side custom events API drew a tidy chart, but the on-call still needs to know which 67 records vanished, whether the counter changed with the latest build, and whether reverting that build will also restore the old alert definition.
Short answer: the best API for a Node.js product-analytics-style metrics dashboard is the one that preserves searchable custom events behind every counter, accepts a small server-side HTTP adapter instead of requiring a full analytics SDK, and lets the producer, query, and alert roll back together. Charts are the last test, not the first.
Start with the page.
An alert is a claim the records must reproduce
It should prove that the page names one broken invariant and carries enough context to test it without browsing a wall of dashboards. For this media pipeline, the invariant is a reconciliation equation for a completed run: eligible input equals searchable output plus documented rejection plus still-pending work. The page payload needs the run identifier, pipeline build, schema version, market, observed totals, completion state, and a link or query reference for the underlying records. A generic events_down page doesn't identify an action.
