Projection troubleshooting over MCP: diagnose → step → read the Apply New in 1.10.0
Diagnose a stalled, lagging or wrong projection — locally with the JasperFx.Events projection-run CLI command, or across a CritterWatch-monitored fleet with the MCP projection tools: diagnose_projection (shards worst-first with verdict, latched error and lag), run_projection_stepper (replay the service's PRODUCTION projection code over a slice of real events and read the per-event before/after state), get_projection_apply_source (the exact Apply overload that ran on the step you flagged).
Use when asked 'why is this projection stuck', 'this read model has the wrong number', 'which event broke the projection', or 'is this projection behind'. Covers the unmeasurable-vs-zero rule (a null gap is not a caught-up shard), the truncation discipline, the chaos-poison cross-check, and the hand-off to a failing-spec-first fix.
Skill details
- Skill name:
wolverine-integrations-critterwatch-projection-troubleshooting - Applies to:
wolverine,marten,polecat,fisher - Tags:
observability,critterwatch,mcp,cli,projections,event-sourcing,daemon,troubleshooting,operations,agents - Added in: 1.10.0
- License: Proprietary. Copyright JasperFx Software LLC.