Dashboard Operations Guide

This guide is for people who keep the dashboard alive.

The dashboard is only as good as the signals behind it.

What Operations Really Means Here

Operating the dashboard means keeping four layers healthy enough to be believable:

  • API;
  • GoCPG;
  • OpenViking;
  • PostgreSQL.

If one of them is weak, the dashboard can still render while telling a partial truth.

What to Watch Operationally

Watch these first:

  • dashboard API health;
  • project sync lag;
  • OpenViking availability;
  • governance database health;
  • freshness of the project snapshots or summaries shown to users.

The Core Rule

Never treat “dashboard page loads” as proof that the dashboard is operationally healthy.

It is healthy only when the underlying signals are current and trustworthy.

Notification Operations

For the notification runtime, the minimum operator path is:

  • run codegraph dashboard notifications bootstrap
  • verify the chosen project is real and has live data
  • remember that test deliveries are not equivalent to live pipeline evidence

That distinction matters because a demo send can succeed while the real page is still empty.

Portfolio Operations

For portfolio operations, keep two things explicit:

  • the historical compare route is POST /api/v2/dashboard/portfolio/compare-periods
  • operators should preserve and verify saved views before they use a comparison or export in a repeated workflow

That keeps the compare result reproducible across Web, REST, CLI, and MCP paths.