The problem is not “Google Analytics for the VPS.” The problem is answering how the factory
is doing without opening five apps. Sigma aggregates 19 live KPIs from DRA, BRI,
RRV, AIF, NLG, TKN, Kronos, SRM, Herald, GHT, PRL, FMR. Each query is try/except — missing table
returns 0, never kills the page. Sigma owns only sigma_alert_rules (auto-create).
14-day DRA+BRI+RRV bar chart. Panels: content pipeline, AI infra cost, platform health (job
success, SRM open, Herald unacked). Rules: metric_key + gt/gte/lt/lte/eq + threshold. Kronos
POST /api/cron/eval-rules fires Herald emit_alert plus a Telegram call
that no-ops without tokens. CSV of all metrics. MCP or login on metric APIs. Refresh every 5
minutes. Nexus is a different pane (health grid, no rules engine).
Adding a metric is a _METRIC_QUERIES entry. Alerting and CSV pick it up. Do not invent a second warehouse.
Not Datadog. Zeros are honest missing tables, not a outage skin.
gt/gte/lt/lte/eq. Evaluated on a schedule, not on this landing.
Nexus polls /health and prefers Sigma API. Sigma is the metric registry.
README still says MiniMax in places; the keys are tkn_cost_*. Do not invent a second billing product.
Will not break if GHT is missing. Public landing is not the KPI JSON.
If you needed per-blueprint drill-in, open that blueprint.
No invented APM traces.
Login for /sigma/app. This page is not live KPI JSON.
Open SigmaRequires a MelTuc account. Create one free.
Cross-platform analytics — pipeline throughput, AI costs, and ecosystem health. Health stays cheap. If this page disagrees with the signed-in app, trust the app — the product contract and tests enforce that rule.