Skip to content

Observability

Posts tagged Observability

10 posts · All posts ➔

24th September 2026CritterWatch 1.1: Run the Console Inside Your Own ApplicationCritterWatch 1.1 adds embedded mode — mount the monitoring console inside the Wolverine application you already run, on the PostgreSQL you already have, with no second deployment and no message broker. Two calls, one database, and the console watches the app it lives in.15th September 2026Wolverine's Production-Capable In-Memory QueuesWolverine's local queues give modular monoliths in-process messaging that's backed by the transactional inbox, durable against process crashes, fully instrumented with OpenTelemetry and metrics, and tunable for sequencing, partitioning, and circuit breaking. Here's why that makes them a much better fit than MediatR notifications.3rd September 2026LLM Callouts in WolverineWolverineFx.AI adds LLM callouts to Wolverine — one-shot calls to a large language model modeled as ordinary messages, so they get the transactional outbox, retries, back pressure, budgets, and testability for free. The first thing JasperFx is building on it is AI Assisted Production Support in CritterWatch 1.1.Interrogating Your Running System with CritterWatch's MCP Server31st August 2026Interrogating Your Running System with CritterWatch's MCP ServerA real, recorded session of an AI agent triaging a Wolverine system through CritterWatch's MCP server — summarizing and replaying dead letters, explaining a message's full journey from its OpenTelemetry spans, chasing down a poisoned projection with the projection stepper, and interrogating the alert subsystem. Plus how the JasperFx AI Skills teach the agent to do all of this well.26th August 2026Alerts and the Timeline in CritterWatch 1.0CritterWatch 1.0 is watching your system for unusual conditions and trying to explain the cause and effect of anything that's going wrong.CritterWatch 1.0: Stop Guessing What Your Critter Stack Is Doing20th August 2026CritterWatch 1.0: Stop Guessing What Your Critter Stack Is DoingCritterWatch 1.0 is here — a monitoring and production-management console purpose-built for Wolverine, Marten, Polecat, and Fisher. It renders the system you actually shipped from the running code, steps through projections event by event, lets you replay dead letters and rebuild projections without a redeploy, and hands your AI agent a real, RBAC-gated control surface.5th August 2026Metadata All the Way Down: Correlation, Causation, and Headers Across Wolverine, Marten, and PolecatEvery serious event sourced system eventually needs to answer 'what caused this event, and who did it?' The Critter Stack establishes correlation, causation, saga, user, and tenant metadata on Wolverine message envelopes — seeded straight from OpenTelemetry activities — then relays all of it onto the events Marten and Polecat store, with storage you can dial from lean to rich.Announcing CritterWatch 1.0 RC 127th July 2026Announcing CritterWatch 1.0 RC 1The first release candidate for CritterWatch 1.0 — a purpose-built monitoring and operations console for the Critter Stack that shows you the system you actually shipped, watches it for you, hands your AI assistant a real control surface, and gives you a proper cockpit for the event store.Introducing CritterWatch: Someone to Keep an Eye on the Critters16th June 2026Introducing CritterWatch: Someone to Keep an Eye on the CrittersCritterWatch 1.0.0-alpha.1 is loose on NuGet — a monitoring and production-management console for Wolverine, Marten, and Polecat that doubles as dev-time insight and an MCP control surface for your AI agents.7th June 2026Announcing CritterWatch 0.8.0CritterWatch 0.8.0 is the largest release yet — a purpose-built monitoring and operations console for the Critter Stack with production observability, development-time insight, and an MCP control surface built for AI agents.