Xitoring Document
Home
FAQ
Support
Register
Home
FAQ
Support
Register
  • Xitoring

    • Introduction
    • Release Notes
    • Xitoring Release Notes
    • Linux Xitogent Release Notes
    • Windows Xitogent Release Notes
    • Xitoring Mobile App Release Notes
    • Account Management
    • API Access & Automation
    • Team Management & Collaboration
    • Billing & Subscription Management
  • Getting Started

    • Getting Started with Xitoring
    • Workflows & Guides
    • Monitor Your First Server
    • Import / Migration
    • Migrate from UptimeRobot to Xitoring
    • Migrate from Pingdom to Xitoring
    • Migrate from Uptime.com to Xitoring
    • Migrate from BetterStack to Xitoring
  • Help & Support

    • FAQ & Troubleshooting
    • Glossary
  • Server Monitoring

    • Server Monitoring
    • Graphs
    • Live Statistics
    • Monitor Services
    • Auto-Triggers
  • Xitogent on Linux

    • Install Xitogent on Linux
    • Update Xitogent on Linux
    • Uninstall Xitogent on Linux
  • Xitogent on Windows

    • Install Xitogent on Windows
    • Uninstall Xitogent on Windows
    • Xitogent Service
    • Update Xitogent on Windows
    • Disk Performance (I/O)
  • Xitogent on Azure

    • Xitogent on Azure
    • Monitor Azure Linux VM
    • Monitor Azure Windows VM
  • Xitogent CLI

    • Xitogent CLI
    • Xitogent Pause/Unpause
    • Xitogent Status
    • Xitogent debug
    • Xitogent Diagnosis
    • Which data we collect
  • Xitoring CLI

    • Xitoring CLI
  • Uptime Monitoring

    • What is Uptime Monitoring
    • Monitoring Nodes (Geographic Locations)
    • What is Check
    • Auto-Discovery
    • Auto Fault Tolerance
    • Heartbeat Check
    • Ping Check
    • HTTP(S) Check
    • DNS Check
    • FTP Check
    • SMTP Check
    • IMAP Check
    • POP3 Check
    • TCP Check
    • UDP Check
  • SSL Monitoring

    • SSL Monitoring
  • Incidents

    • Incidents
    • Incident's Root Cause
    • Incidents Notification
    • Incident Notes
    • Resolving Incidents Manually
    • Incident Policy
  • Maintenance Schedule

    • Maintenance Schedule
  • Email Reports

    • Email Reports
  • Integrations

    • Integrations
    • Apache Integration
    • CoreDNS Integration
    • CouchDB Integration
    • Disk Health Integration
    • Docker Integration
    • Dovecot Integration
    • Exim Integration
    • HAProxy Integration
    • IIS Integration
    • InfluxDB Integration
    • Kafka Integration
    • KeyDB Integration
    • LiteSpeed Integration
    • MongoDB Integration
    • MySQL Integration
    • Netstat Integration
    • Nginx Integration
    • OpenLiteSpeed Integration
    • OpenVPN Integration
    • PHP-FPM Integration
    • Postfix Integration
    • PostgreSQL Integration
    • RabbitMQ integration
    • Redis Integration
    • MS SQL Server Integration
    • Supervisor Integration
    • Varnish Integration
    • Wireguard Integration
  • Notifications

    • Notifications
    • Creating Notification Roles
    • Email Integration
    • Mobile Push Notifications
    • SMS Integration
    • Phone call Integration
    • Webhook Integration
    • Integration for Slack
    • Telegram Integration
    • WhatsApp Integration
    • Mattermost Integration
    • Discord Integration
    • Google Chat Integration
    • Microsoft Teams Integration
    • Atlassian Opsgenie Integration
    • Splunk On-Call Integration
    • Pushover Integration
    • Pushbullet Integration
    • Gotify Integration
    • Ntfy Integration
    • Spike.sh Integration
    • PagerDuty Integration
    • Zapier Integration
    • AlertOps Integration
  • Status Page

    • Status page
  • 3rd Party Status Pages

    • Using 3rd party Status Pages
    • Atlassian Status Page Integration with Xitoring
    • Status.io Integration with Xitoring
    • Statuspal Integration with Xitoring
    • Instatus Integration with Xitoring
  • Dashboards

    • Main Dashboard
    • Custom Dashboards
  • Metrics

    • Metrics
  • MCP Server

    • Setup & Tool Reference

KeyDB Integration

KeyDB is a widely used open-source in-memory database that is known for its speed, flexibility, and high availability. It is designed to function as a drop-in replacement for Redis, offering better performance and scalability for large-scale applications. KeyDB supports various data structures such as strings, hashes, lists, sets, and sorted sets, and provides advanced features such as pub/sub messaging, Lua scripting, and transactions.

Monitoring KeyDB is crucial to ensure its availability, performance, and security in many applications. Xitoring provides a comprehensive monitoring solution for KeyDB that allows users to monitor critical performance metrics such as memory usage, CPU utilization, throughput, and latency. Additionally, Xitoring provides advanced alerting capabilities that promptly notify users of any issues, empowering them to address problems proactively before they impact end-users. Monitoring KeyDB with Xitoring helps to ensure the reliability and performance of KeyDB-based applications, reducing downtime and enhancing the user experience.

Supported platforms

The following guide is working on Linux but some details could be quite different based on the OS version.

Enable KeyDB integration

Enabling Integrations with Xitogent is a straightforward process, and adding KeyDB integration is no exception. Xitogent offers a step-by-step CLI wizard that guides users through the process, allowing them to enable KeyDB integration quickly.

To add KeyDB integration using Xitogent, simply run the following command on the server:

xitogent integrate

From the list of available integrations, select KeyDB. Xitogent will prompt for the password of your KeyDB CLI so that it can connect to KeyDB, gather information, and collect statistics. If you are not using a password for your KeyDB CLI, you can leave the password field blank and hit enter. Xitogent will automatically connect to your KeyDB on port 6379 using the given password and send statistics that you can see in the Xitoring app.

After successful integration, Xitogent will create a configuration file for KeyDB integration at /etc/xitogent/integrations/keydb_integration.conf. The configuration file will contain important statistics such as total reads processed, total writes processed, and the last update timestamp.

Setup Triggers for KeyDB integration

Xitogent also enables users to create Triggers for KeyDB integrations and set up incidents based on specific parameters. These parameters include:

Connected clients
Rejected conns
R per sec (Read per second)
W per sec (Write per second)
Used memory
Used CPU user
Total keys

For instance, users can create a Trigger for Total keys that generates an incident if the total number of keys exceeds a specific threshold. On the Trigger page, users can view the current value for each parameter and configure their alerts accordingly.

Last Updated: 4/12/23, 8:04 PM
Prev
Kafka Integration
Next
LiteSpeed Integration