SQL over the event store, through the console New in 1.14.0
Run one read-only SQL SELECT against any monitored service's event-store database through CritterWatch's query_sql MCP tool — the escape hatch beside query_events for the join, the GROUP BY and the per-stream count the structured filters cannot express. The statement executes on the monitored service, on its own connection, inside a read-only transaction that is always rolled back; no database credentials, one license/RBAC/audit pipeline.
Use when a question needs a projection document table, a payload field aggregate, a tag table, or any shape query_events cannot ask. Covers when to reach for SQL instead of the filters, writing for the target store's dialect (PostgreSQL / T-SQL / SQLite) and the table names each store declares, the allow-list refusal as a table catalog, the row cap and timeout honesty fields, @name parameters, typed cells, fleet addressing (storeUri required on a multi-store service; tenantId / databaseIdentifier on a multi-database store), the mcp.sql.query capability and the audit trail, and the Explorer SQL view as the human twin.
Skill details
- Skill name:
wolverine-integrations-critterwatch-sql-query - Applies to:
wolverine,marten,polecat,fisher - Tags:
observability,critterwatch,mcp,event-sourcing,event-store,querying,sql,diagnostics,agents - Added in: 1.14.0
- License: Proprietary. Copyright JasperFx Software LLC.