Dashboard and Operations

Dashboard and Operations

The built-in /dashboard interface brings together the operational views needed to understand a running MemCP instance: CPU and memory metrics, requests, databases and tables, shard and compression details, SQL and Scheme consoles, users and grants, runtime settings, active processes, service state, and configured logs.

Inspecting and stopping work

Use SHOW PROCESSLIST or SHOW FULL PROCESSLIST from SQL to inspect current connections and queries. KILL QUERY cancels a running statement while leaving its connection available; KILL CONNECTION closes the session. The dashboard exposes the same operational controls.

Cancellation is cooperative. A query must reach a cancellation-aware planner or storage boundary before it stops. During graceful shutdown MemCP rejects new work and waits up to ShutdownDrainSeconds for in-flight requests.

Metrics and logs

Optional MetricsTracing records periodic runtime samples. ErrorQueryLog stores failed SQL and PrintLog captures Scheme print/time output; both have configurable retention limits. Because SQL text, parameters, identifiers, or application data can occur in these logs, restrict access and choose limits appropriate to the workload.

Monitor at least:

• current memory use versus total and persistent-data budgets;
• eviction and cold-column reload activity;
• active and failed requests, latency, and cancellations;
• WAL, rebuild, checkpoint, and restart behavior;
• local or remote storage latency and errors;
• connection count and long-running transactions.

Production boundaries

Protect the dashboard with strong credentials, TLS at a trusted proxy, and network controls. It is an inspection surface, not a replacement for backups, external health checks, alerting, capacity planning, or restore tests. See Settings, Security and Authentication, Memory Management and Eviction, and Performance Measurement.