Event Store

The Event Store view provides direct visibility into the Marten event streams that power CritterWatch's internal state. It also surfaces event store information from monitored services that use Marten for their own domain events.

CritterWatch Internal Event Streams

CritterWatch stores all service state as Marten events. Each monitored service gets its own event stream keyed by service name. The Event Store view lets you inspect these streams directly.

Stream Browser

Browse event streams by service name. Each stream entry shows:

• Stream ID — the service name (e.g., trip-service)
• Event Count — total number of events in the stream
• Last Event — type and timestamp of the most recent event
• Version — current aggregate version

Click a stream to open the event list.

Event List

Events are displayed in chronological order with:

Column	Description
Sequence	Global event sequence number
Version	Version within this stream
Event Type	The .NET type name of the event
Timestamp	When the event was written
Data	Expandable JSON payload

Common event types in the CritterWatch stream:

Event	Meaning
ServiceRegistered	Service first appeared and registered
NodeAdded	A new process node joined
NodeRemoved	A node stopped reporting
AgentStarted	An agent began on a node
AgentStopped	An agent stopped
ShardStatesUpdated	Projection shard states changed
EndpointAdded	A new messaging endpoint was discovered
TenantAdded	A tenant was added at runtime
VersionDetected	Wolverine version updated

Stream Queries

Filter the event list by:

• Event Type — show only specific event types
• Time Range — events written within a specific window
• Version Range — events between two stream versions

Monitored Service Event Stores

For services that use Marten as their own event store, CritterWatch displays high-level event store metrics reported by the Wolverine.CritterWatch observer:

• Store URI — the PostgreSQL connection (host and database)
• Schema — Marten schema name
• Global Sequence — the current high water mark
• Last Activity — timestamp of the most recently written event

This provides visibility into the event store health of your domain services without CritterWatch needing direct database access.

Event Store Access

CritterWatch only has direct access to its own Marten event store. Metrics from monitored services' event stores are self-reported by the Wolverine.CritterWatch observer and may be a few seconds stale.