# BetterDB-inc/monitor

Source: https://glimind.com/server/awesome%2Fbetterdb-inc%2Fmonitor
Registry id: `awesome/betterdb-inc/monitor`
Status: unknown

## Tools (60)

- `add_connection`: Add a new Valkey/Redis connection to BetterDB. Optionally set it as the active default.
- `ai_instance_history`: Get the stored metrics time-series for one AI component instance (hits, misses, hit rate, cost saved, evictions, item count, index size, threshold). Use ai_list
- `ai_list_instances`: List AI component instances (semantic caches, agent caches, agent memory stores, retrieval pipelines) auto-discovered on the connected Valkey/Redis instance, wi
- `cache_approve_proposal`: Approve a pending proposal. Synchronously applies the change to Valkey and returns the terminal status (applied|failed). Idempotent: a second call on an already
- `cache_edit_and_approve_proposal`: Edit an existing pending proposal and approve it in one step. Provide exactly one edit field matching the proposal type: new_threshold for threshold_adjust, new
- `cache_get_proposal`: Fetch a single cache proposal by id, including its audit trail.
- `cache_health`: Detailed health for a single cache. Response branches by type: semantic_cache reports category_breakdown + uncertain_hit_rate; agent_cache reports tool_breakdow
- `cache_list`: List all caches (semantic_cache and agent_cache) registered for the active instance, with hit rate and total ops.
- `cache_list_pending_proposals`: List pending cache proposals for the active instance, newest first. Optionally filter by cache_name.
- `cache_propose_invalidate`: Propose a cache invalidation for review. Filter shape depends on cache type: semantic_cache requires filter_kind=valkey_search + filter_expression; agent_cache 
- `cache_propose_threshold_adjust`: Propose a semantic-cache similarity-threshold change for review. Creates a pending proposal that requires human approval before any change is applied. Reasoning
- `cache_propose_tool_ttl_adjust`: Propose an agent-cache per-tool TTL change for review. Creates a pending proposal that requires human approval. Reasoning must be at least 20 characters.
- `cache_recent_changes`: Recent proposals for a single cache (any status), so agents can avoid re-proposing pending or recently-applied changes. Newest first.
- `cache_reject_proposal`: Reject a pending proposal. Optionally records a reason in the audit trail.
- `cache_similarity_distribution`: Histogram of recent similarity scores (20 buckets, width 0.1) for a semantic_cache. Errors on agent_cache.
- `cache_threshold_recommendation`: Threshold-tuning recommendation for a semantic_cache, based on the rolling similarity-score window. Errors with INVALID_CACHE_TYPE on agent_cache.
- `cache_tool_effectiveness`: Per-tool hit rate, cost saved, and TTL recommendation for an agent_cache. Errors with INVALID_CACHE_TYPE on semantic_cache.
- `correlate_ai_trace`: Explain WHY a trace behaved the way it did by joining its cache/memory spans with live Valkey state: does the key still exist, what is its TTL, what threshold w
- `get_acl_audit`: Get persisted ACL audit log entries from storage. Filter by username, reason (auth, command, key, channel), or time range. Use this to investigate why a connect
- `get_ai_trace`: Get the full span waterfall for one AI trace: every span with timing, parent relationships, and attributes (model, cache hit/miss, similarity scores). Use list_
- `get_anomalies`: Get anomaly detection events from persisted storage. BetterDB continuously runs Z-score analysis on memory, hit rate, CPU, and other metrics — this returns the 
- `get_client_activity`: Get time-bucketed client activity from persisted snapshots. Shows connection counts, command distribution, and buffer usage over time. Use startTime/endTime to 
- `get_clients`: Get the active client list with connection details.
- `get_cluster_node_stats`: Get per-node performance stats: memory usage, ops/sec, connected clients, replication offset, and CPU. Use this to identify hot nodes, lagging replicas, or unev
- `get_cluster_nodes`: Discover all nodes in the Valkey cluster — role (master/replica), address, health status, and slot ranges. Returns an error message if this instance is not runn
- `get_cluster_slowlog`: Get the aggregated slowlog across ALL nodes in the cluster. This is the primary tool for finding slow commands in cluster mode — per-node slowlogs are incomplet
- `get_commandlog`: Get the most recent entries from COMMANDLOG (Valkey 8+ only, superset of slowlog).
- `get_commandlog_history`: Get persisted COMMANDLOG entries from storage (Valkey 8+ only). Supports time range filtering to investigate specific incidents. Returns empty with a note if CO
- `get_commandlog_patterns`: Get analyzed COMMANDLOG patterns from persisted storage (Valkey 8+ only). Like get_slowlog_patterns but includes large-request and large-reply patterns in addit
- `get_forecast`: Get a capacity forecast for one metric: current trajectory and projected time until the resource ceiling is hit. Metric kinds: opsPerSec, usedMemory, cpuTotal, 
- `get_health`: Get a synthetic health summary for the active instance: keyspace hit rate, memory fragmentation ratio, connected clients, replication lag (replicas only), and k
- `get_hot_keys`: Get hot key tracking data from persisted storage. BetterDB periodically scans keys using LFU frequency scores (when maxmemory-policy is an LFU variant) or OBJEC
- `get_inference_latency`: Get the FT.SEARCH latency profile: p50/p95/p99 per vector index over the sampling window, plus SLA breach status per index. sla is null when BetterDB Pro infere
- `get_info`: Get INFO stats for the active instance. Contains all health data: memory, clients, replication, keyspace, stats (hit rate, ops/sec), and server info. Optionally
- `get_largest_keys`: Get the largest keys from key analytics snapshots, ranked by measured memory usage. Coverage note: snapshots track the biggest collections by element count, so 
- `get_latency`: Get latency event history for the active instance.
- `get_latency_history`: Get the full latency history for a named event (e.g. 'command', 'fast-command'). Call get_latency first to see which event names are available, then use this to
- `get_latency_regressions`: Get detected latency regressions (sustained p99 command-latency degradations vs baseline) from persisted storage. Companion to get_anomalies: same event store, 
- `get_memory`: Get memory diagnostics: MEMORY DOCTOR assessment and MEMORY STATS breakdown.
- `get_slot_stats`: Get per-slot key counts and CPU usage (Valkey 8.0+ only). Use orderBy='cpu-usec' to find hot slots, or 'key-count' to find the most populated slots. Returns an 
- `get_slowlog`: Get the most recent slow commands from the slowlog.
- `get_slowlog_patterns`: Get analyzed slowlog patterns from persisted storage. Groups slow commands by normalized pattern, showing frequency, average duration, and example commands. Sur
- `get_vector_indexes`: Get health details for every vector search index on the instance: document count, memory usage, indexing failures, and percent indexed. Requires the Search modu
- `list_ai_traces`: List recent AI application traces ingested via OpenTelemetry (LLM calls, cache lookups, memory recalls, retrieval spans). Not tied to a Valkey instance — traces
- `list_instances`: List all Valkey/Redis instances registered in BetterDB. Shows connection status and capabilities.
- `memory_approve_forget`: Approve a pending forget proposal, applying the deletion against the live store.
- `memory_forget`: Propose forgetting memories (by id, or by scope/tags). Creates a pending proposal that a human must approve before anything is deleted.
- `memory_get`: Fetch a single memory by ID from a store.
- `memory_list`: List memories in a store, newest first, with optional scope and tag filters.
- `memory_list_pending_forgets`: List pending forget proposals awaiting approval on an instance.
- `memory_recall`: Recall memories from a store by a precomputed query vector (the caller supplies the embedding).
- `memory_reject_forget`: Reject a pending forget proposal without deleting anything.
- `memory_stats`: Get item count, eviction count, and live config for a memory store.
- `memory_stores`: List agent-memory stores discovered on an instance (name, capabilities, stats key).
- `remove_connection`: Remove a connection from BetterDB.
- `select_instance`: Select which instance subsequent tool calls operate on.
- `set_default_connection`: Set a connection as the active default for BetterDB.
- `start_monitor`: Start the BetterDB monitor as a persistent background process. If already running, returns the existing URL. The monitor persists across MCP sessions and must b
- `stop_monitor`: Stop a persistent BetterDB monitor process that was previously started with start_monitor or --autostart --persist.
- `test_connection`: Test a Valkey/Redis connection without persisting it. Use before add_connection to validate credentials.

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.