Event-store querying over MCP: what actually happened Added in 1.11.0
Query the raw events in any monitored service's event store through CritterWatch's query_events MCP tool — the write-side 'what actually happened' half of projection troubleshooting, and the store-agnostic path that works identically on Marten (PostgreSQL), Polecat (SQL Server), and Fisher (SQLite) with no database credentials.
Use when verifying a command emitted the events you think it did, isolating one message chain's appends by correlation id (integration-test forensics), chasing causation across streams, running DCB tag queries, or counting events by type. Covers the two query paths and why they still cannot be combined, the broadened metadata filters (multi-type unions, timestamp and sequence windows), the FilterMismatch guard against results that look filtered but are not, the totalCount counting discipline, fleet addressing (serviceName/storeUri/tenantId), error literacy (NoResponse is never 'no events'), the event-query CLI twin for the no-console path, and the direct-SQL recipe per store.
Skill details
- Skill name:
wolverine-integrations-critterwatch-event-query - Applies to:
wolverine,marten,polecat,fisher - Tags:
observability,critterwatch,mcp,event-sourcing,event-store,querying,dcb,correlation,diagnostics,agents,cli - Added in: 1.11.0
- License: Proprietary. Copyright JasperFx Software LLC.