Event Store

The Event Store view is for forensics — when you want to know "what was the state of this service at time T" or "what was the exact sequence of events leading up to that incident."

It's the deepest read-only surface in the console. Most operational work happens on the Dashboard, Services, and Alerts pages; reach for the Event Store when those don't have enough resolution.

What you can browse

CritterWatch keeps a per-service stream of every notable change — node lifecycle, agent assignments, projection shard advances, endpoint discovery, tenant additions, version detections, and the rest. The Event Store view lets you walk those streams.

Stream Browser

The browser lists each monitored service as a stream. For each:

• Stream ID — the service name (e.g., trip-service).
• Event Count — total events recorded for this service.
• Last Event — type and timestamp of the most recent event.

Click a stream to open the event list.

Event List

Events appear in chronological order with:

Column	Description
Sequence	Global event sequence number
Version	Version within this stream
Event Type	Human-readable event name (NodeAdded, AgentStarted, ...)
Timestamp	When the event was recorded
Data	Expandable JSON payload

Filter the list by:

• Event Type — focus on a category (e.g., only AgentStarted / AgentStopped).
• Time Range — events within a specific window.
• Version Range — events between two stream versions, useful when you know exactly which transitions you want to inspect.

What to look for

Common forensic patterns:

Question	Where to look
When did the leader change?	Filter by LeadershipAssumed / leadership-related events.
Did this projection rebuild already, or did the operator just click Rebuild?	Filter for SubscriptionOrProjectionRestartedEvent and similar shard events.
When did this tenant get added?	Filter for TenantAdded.
Did we deploy a new Wolverine version recently?	Filter for VersionDetected.

Monitored-service event stores

For services that use Marten as their own event store (e.g., for your domain events), CritterWatch surfaces high-level metrics reported by the service itself:

• Store URI — PostgreSQL host and database
• Schema — Marten schema name
• Global Sequence — the current high-water mark
• Last Activity — when an event was last written

This is read-only metadata. CritterWatch doesn't have direct access to your service's event store and doesn't render the events inside it. To browse those events, use Marten's tooling against the database directly.

Limits of the view

• CritterWatch's own streams are the ones you can browse directly here — they describe the operational state of each service.
• Your service's domain event stream is reported via metrics only (sequence, last activity). The events inside live in your application's database.