PostgreSQL
Sessions, locks, queries, tables, indexes and a console. Query statistics come from pg_stat_statements when it is installed.
OverviewSessionsLocksQueriesTablesIndexesConsoleEach engine has its own way of working. Recern follows it, with views built around how each one runs instead of a generic table browser.
Sessions, locks, queries, tables, indexes and a console. Query statistics come from pg_stat_statements when it is installed.
OverviewSessionsLocksQueriesTablesIndexesConsoleMemory, clients, the slow log and keys, with a console that knows which commands only read.
OverviewMemoryClientsSlow logKeysConsoleThe Redis views, with Valkey recognised when you connect.
OverviewMemoryClientsSlow logKeysConsoleThe Redis views for Dragonfly, recognised when you connect.
OverviewMemoryClientsSlow logKeysConsoleOpen a .rvec file to see its collections, the HNSW graph and recall measured against exact search. Recern only reads the file.
OverviewIndexRecallCollections, documents, operations, indexes and query efficiency.
Queries, parts, merges, mutations and replicas.
Sessions, locks, queries, InnoDB and replication.
Tables, indexes, pragmas and storage of a file on your disk.
Keyspaces, tables, compaction and the health of every node.
Vector indexes in PostgreSQL: whether queries use them, their memory and real recall.
Collections, segments and recall of a vector-native engine.
The order can change. Tell us which database you need next: [email protected]