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

Redis Integration

Redis is a popular open-source in-memory data structure store that is used as a database, cache, and message broker. It is known for its speed, flexibility, and high availability, making it a popular choice for many types of applications.

Given its importance in many applications, it is critical to monitor Redis to ensure its availability, performance, and security. Xitoring Redis integration provides a comprehensive monitoring solution for Redis, allowing users to monitor key performance metrics such as memory usage, CPU utilization, throughput, and latency. Xitoring also offers advanced alerting capabilities that notify users of issues in real-time, enabling them to proactively address problems before they impact end-users. Overall, monitoring Redis with Xitoring can help ensure the reliability and performance of Redis-based applications, while reducing downtime and improving 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 Redis Integration

Enabling Integrations are very easy task as Xitogent offers a step-by-step CLI wizard that helps you enable Integrations in no time, For Redis, you just need to call Xitogent CLI on the server you want to add Redis integration for with the following command:

xitogent integrate

and from the list of available integrations select Redis.

It will ask you for the password of your Redis CLI so Xitogent can connect to Redis and gather information and statistics, Also if you are not using any password for Redis CLI you just need to leave the password blank and hit enter. it will automatically connect to your Redis on port 6379 using the given password and send statistics that you can see in the Xitoring app.

Now the configuration file is created in the /etc/xitogent/integrations/redis_integration.conf and the content of the config file is something like the below:

password=myredispassword

Setup Triggers for Redis integration

You can create Triggers for Redis integrations and define incidents for the following parameters:

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

For example, you create a Trigger for Total keys to give you an incident if your Total key number goes further than a specific number, In the trigger page you can also see the current value for each of the parameters.

Last Updated: 4/3/23, 7:21 PM
Prev
RabbitMQ integration
Next
MS SQL Server Integration