Troubleshooting

Point your coding agent at a running RavenDB cluster over MCP. Twenty-one read-only tools, one environment variable, and it reads the cluster instead of guessing.

Use the RavenDB Debug Package Analyzer in the Studio to diagnose a misbehaving cluster you cannot connect to. Read the cluster, node, and database panels of a debug package to move from symptom to cause without handling production data.

Learn how to use the RavenDB ETL Errors View in Studio to diagnose and fix ETL pipeline issues, including script errors, connection failures, and transformation problems.

Learn how to use RavenDB Studio's Cluster Dashboard, Traffic Watch, Admin Logs, and other built-in tools to diagnose and investigate database performance issues.

Why RavenDB queries can return stale results, when that is perfectly fine, and how to force fresh results per query, per session, or across the whole document store.

Trace live and historical requests to your RavenDB cluster with Traffic Watch, Admin Logs, Studio notifications, and Audit Logs to diagnose unexpected activity and performance issues.

Track down the RavenDB index that's consuming your disk I/O using the Studio Indexing Performance view, iotop on Linux, and Resource Monitor on Windows, then optimize the culprit.

Diagnose and fix high memory usage in RavenDB: understand how RavenDB manages memory with memory-mapped files, spot trouble on Windows, Linux, and in the Studio, then trace the cause with admin logs, debug endpoints, and dotnet-dump.

Track down what drives RavenDB's CPU load. Tell Current CPU Usage from Total CPU Time, then diagnose it with top, htop, and RavenDB Studio.