Overview
KeyDB is a high-performance, open-source in-memory database designed as a drop-in replacement for Redis, offering better performance and scalability for large-scale applications. Xitoring's KeyDB integration monitors critical metrics like memory, CPU, throughput, and connections — ensuring your KeyDB instances stay fast and reliable.
What Can It Monitor?
- Connected Clients — Number of active client connections
- Rejected Connections — Connections refused due to maxclients limit
- Reads per Second — Rate of read operations
- Writes per Second — Rate of write operations
- Used Memory — Total memory consumed by KeyDB
- Used CPU (User) — CPU time spent on user-space operations
- Total Keys — Total number of keys across all databases
Prerequisites
- KeyDB installed and running on your Linux server
- Xitogent agent installed
- KeyDB CLI password (if authentication is enabled)
No additional modules or configuration changes are required.
How to Activate the Integration
Run the Xitogent CLI:
xitogent integrate
Select KeyDB from the list of available integrations. When prompted, enter your KeyDB CLI password. If no password is configured, leave it blank and press Enter.
Xitogent automatically connects to KeyDB on port 6379 and begins collecting statistics.
The config file is created at /etc/xitogent/integrations/keydb_integration.conf.
Setting Up Triggers
Available trigger parameters:
- Connected Clients
- Rejected Connections
- Reads per Second / Writes per Second
- Used Memory
- Used CPU (User)
- Total Keys
Navigate to Triggers on your server page, select KeyDB, choose a metric, set your threshold, and configure notifications.
Tips
- KeyDB is a drop-in Redis replacement, so monitoring patterns are similar
- Monitor Used Memory to prevent out-of-memory issues
- Set alerts on Rejected Connections to detect when client limits are too low
- Track Reads/Writes per Second to understand workload patterns
- Currently supported on Linux servers