/ops) is a platform-wide operations interface built for teams running LangWatch on their own infrastructure. It gives operators real-time visibility into the event-sourcing pipeline, queue health, processing throughput, error clusters, and the tools to act on problems without touching the database or restarting pods.
When to Use Ops
Feature Overview
Dashboard
Real-time throughput, latency, error rates, and pipeline health at a glance. Powered by Server-Sent Events with automatic polling fallback.
Queue Management
Error groups, blocked queues, dead letter queue redriving, draining, and pipeline pause/unpause controls.
Projection Replay
Rebuild projection state by replaying events from ClickHouse. Supports bulk replay across tenants, single-aggregate debugging, and dry runs.
Deja View
Time-travel debugger for event-sourced aggregates. Inspect the full event history and compute any projection’s state at any point in time.
The Foundry
Interactive trace playground for building, visualizing, and sending synthetic traces to any project. Useful for testing ingestion pipelines and reproducing issues.
Access Control
The Ops Console uses two dedicated permissions, separate from project-level RBAC:
These are platform-wide permissions, not scoped to a specific project. Users without
ops:view are redirected away from /ops routes.
See Access Control (RBAC) for details on assigning permissions.
Architecture Context
The Ops Console sits on top of LangWatch’s event-sourcing pipeline:- Commands enter Redis queues from the ingestion API
- Workers consume commands, emit events, and update projections in ClickHouse
- The Ops Console reads queue state from Redis and event history from ClickHouse, and can issue control actions (unblock, drain, pause, replay) back to the queues