Event Store
This page has moved
There is no longer a standalone Event Store page. The old /events route now redirects into the Event Store Explorer (its Event Explorer tab), and router.push({ name: 'events' }) still resolves there, so old bookmarks keep working.
"Event Store" is one of three similarly-named console surfaces that are easy to confuse. Here is what each one actually reads, so you land on the right one:
| Surface | Route | What it reads |
|---|---|---|
| Event Store Explorer | /explorer | A monitored service's event store — its domain streams, events, projections, and event-store configuration. This is where the old "Event Store" browsing lives now. |
| Store Inspector | /raw | The console's own frontend state — every Pinia store the SPA holds plus a live SignalR message log. A debugging surface, not a data browser. |
| Timeline + Audit Log | /timeline, /audit-log | CritterWatch's own operational history — system events (node/agent/leadership/tenant changes) on the Timeline, and operator-initiated actions on the Audit Log. |
Where the old page's jobs went
The retired page tried to be two things at once — a window into the monitored app's events and a log of CritterWatch's own operational events. Those are now separated:
- "What happened inside my service's event store?" → Event Store Explorer (browse streams, read events, inspect projection status, and step a projection's replay event-by-event with the Projection Stepper).
- "When did the leader change / this tenant get added / a new version get detected?" → Timeline — CritterWatch's own chronological system-event feed.
- "Who clicked Rebuild / Pause / Discard, and when?" → Audit Log — the record of operator-initiated actions.