Setting Up CritterWatch Added in 1.2.0
Install and configure CritterWatch, the monitoring console for Wolverine, Marten, Polecat and Fisher apps, on any of its three store flavours (CritterWatch, CritterWatch.SqlServer, CritterWatch.Sqlite for Fisher/SQLite). Covers single-node and clustered hosts (Redis SignalR backplane, sharded transport topology), .NET Aspire with the CritterWatch.Aspire AppHost package (AddCritterWatch, WithCritterWatch, WithCritterWatchMcp, WithJasperFxLicense), the broker-less channels of 1.1.0 (Wolverine's HTTP transport with UseHttpTransport and the /_wolverine/batch/{queue} routes, gRPC with ListenAtGrpcPort, PostgreSQL or SQL Server queues as an ancillary store, and the two startup refusals), the CritterWatch.Mcp server and its 1.1 safety rails (read-only mode, confirmation tokens and confirmationRequired previews, the audit log's Mcp channel), metrics sizing and delete_metrics_samples, licensing, opt-in RBAC and the 1.2 capability catalog (console actions checked like their MCP twins, dlq.triage, documents.watch, mcp.sagas.read, service.license-slot, projection-stepper.view), get_command_outcome, multi-tenant deployments, the multi-transport BFF, and the 1.1 embedded console (AddCritterWatchEmbedded / UseCritterWatchEmbedded, keeping tracked sessions and Bobcat specs working beside it).
Use when adding CritterWatch to an application, embedding the console in an app, or standing up a new monitoring console.
Skill details
- Skill name:
wolverine-integrations-critterwatch-setup - Applies to:
wolverine,marten,polecat,fisher - Tags:
observability,critterwatch,mcp,rbac,clustering,multi-tenancy,diagnostics,cli,aspire,sqlite,fisher,read-only,confirmation,audit,licensing,capabilities,sagas,command-outcome - Added in: 1.2.0
- License: Proprietary. Copyright JasperFx Software LLC.
