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.
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:
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:
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.