Debugging production over SSH
A customer reports a stuck export. The on-call answer is log grep and hand-written queue queries at 11 p.m. There's no single view of what actually needs an operator right now.
Eén scherm toont wat gezond is, wat faalde en hoe de zaak ervoor staat.
Eén scherm toont wat gezond is, wat faalde en hoe de zaak ervoor staat.
Productvoorbeeld
Dit is hetzelfde visuele component als in de ingelogde applicatie, met voorspelbare voorbeelddata.
See an open incident, a delayed process, and a dead outbox event in the same tenant-scoped workbench.
Inerte voorbeelddata · geen netwerktoegang
Owner-only, tenant-scoped operational signals.
Stable fingerprints group recurring conditions; acknowledgements, resolutions, and linked recovery actions remain durable.
Bounded tenant records and safe failure classes only. Provider payloads, response bodies, object names, and raw errors stay hidden.
Recent commands show accepted work through terminal settlement. Trend buckets contain counts only, never identifiers or provider payloads.
Configuration and runtime evidence are separate. “Not verified” never implies that credentials or the live provider are healthy.
Voorbeeld gereed
Zonder een gedeelde basis bouwt elk team deze randgevallen opnieuw — en anders.
A customer reports a stuck export. The on-call answer is log grep and hand-written queue queries at 11 p.m. There's no single view of what actually needs an operator right now.
Re-firing a webhook from a REPL or flipping a status column in psql skips every safety check and leaves no trail. It works, until the day it quietly creates a bigger mess than the one it fixed.
Dead jobs in one dashboard, failed webhooks in another, stuck uploads in a third. Nothing connects a failure to the fix that handled it, so the same fire gets fought twice.
Kernpunten
Failed jobs, dead work, webhook errors, storage issues, and billing backlog are grouped by the action each one needs.
Every fix runs through the same guarded path the feature itself uses. Clicking twice can't run it twice.
Each action records who did what and when, and gets tracked until it actually settles.
Het mechanisme van begin tot eind, zoals het in de repository is geïmplementeerd.
Owners only
The server resolves the active company and checks who you are. Anyone who isn't a current organization owner gets a 404, not a hint the page exists.
Trouble is sorted into lanes
Failures are grouped by the action they need and capped at eight per lane. Details are reduced to safe summaries; raw payloads and provider errors never reach the screen.
Fixes reuse the safe path
Retry, requeue, and replay call the same protected command the feature itself uses. The action, its receipt, and its audit record all save together in one step.
Every fix is watched to the end
A background check tracks each action until it truly settles or fails, and the screen tells you how fresh its data is instead of faking it.
Technische garanties
Achter de schermen houden autorisatie, tenantgrenzen en foutafhandeling één duidelijke eigenaar. Zo blijft de snelle ervaring voor gebruikers gekoppeld aan veilig herstel als het misgaat.
De grens hierboven is geen claim maar code. Deze bestanden dragen het contract:
src/modules/control-center/MODULE.mdsrc/modules/control-center/server.tssrc/modules/control-center/operations.server.tsDeze functies delen contracten en grenzen met deze pagina.
De documentatie beschrijft dezelfde contracten die deze pagina demonstreert.