Are you using Redis in your application? You can use IDERA Uptime Cloud Monitor(UCM) to monitor your Redis performance. As an illustration, you can configure and receive alerts for the following scenarios:
Uptime Cloud Monitor from IDERA offers a SAAS based out-of-the-box monitoring solution for Redis that is easy to set up. If you are not familiar with the concept of custom metrics as used in Uptime Cloud Monitor, please go through Custom Metrics information once before continuing with this document.
There are three steps that you need to do to start monitoring a Redis server:
Figure 1: In your Uptime Cloud Monitor Account, navigate to Databases>Getting Started
Login to your Uptime Cloud Monitor account and navigate to Custom tab -> Getting Started. Click on Redis icon.
Figure 2: The Redis agent installation script
Click on icon to copy the installer script to your clipboard. Paste the command into the terminal window on the server where you want to install the agent. Script can be run on the server running Redis, or it can be a different server, but this server will need to be continually running in order to monitor Redis.
As soon as the script is run on a terminal with root access, it starts downloading the required Redis monitoring agent on your server. You will need to configure the following items in the agent installation process. Item specified in square brackets ( [ ] ) are the default.
Figure 3: Executing the Redis agent installation script
1. Press y to monitor Redis.
Figure 4: Executing the Redis agent installation script with user as copperegg, Group as copperegg and monitoring frequency as 15 seconds
2. Monitoring frequency: 15, , 300, 900, 3600 seconds
3. User and Group for running service as default values: [copperegg][copperegg]
Figure 5: Executing the Redis agent installation script with group name as “Redis”, group label as “Redis Metrics” and Dashboard as “Redis”
4. Group label, group name and dashboard name for custom metrics [Redis][Redis Metrics][Redis]
Figure 6: Executing the Redis agent installation script with unique id, server hostname and port. Only one Redis server is added for monitoring.
5. Unique name for this node (good to differentiate if you are monitoring different Redis databases). [<user>-Redis]
6. Server details : hostname and port for service. [localhost]
7. After configuring one database, you’ll get an option to add more Redis server.
Figure 7: Executing the Redis agent installation script with an upstart init file and the default value for log file name. The installation completes successfully!
8. Configure log file name and upstart job name (defaults present) [/usr/local/copperegg/log/copperegg-metrics.log][/etc/init/copperegg-metrics.conf]
Navigate to Dashboard and you will see a new Redis Dashboard has been added automatically by the installer.
Figure 8: A new Dashboard for Redis has been added
As the installed script executes, you will notice data samples appearing on the widgets for this Dashboard.
Figure 9: Widget inside Redis Dashboard displaying Uptime.
Figure 10: Widget inside Redis Dashboard displaying connected clients.
Figure 11: Widget inside Redis Dashboard displaying used memory.
Uptime Cloud Monitor currently monitors 22 metrics which cover most of the important metrics for Redis from a performance and stability perspective. You can see these 22 metrics by navigating to the Custom Tab > Custom Objects and selecting Details on the Custom Metrics Group Label [Redis Metrics] that was given as installation input. For some of these metrics, alerts have been automatically created (see section 3 below). To create new alerts see the section "Configuring your own Alerts for Redis database" below.
The metrics are:
As soon as your Redis Database Monitoring Dashboard comes up, you will notice that some alert configurations have been automatically created by our Installation Script (under Alerts > Configure Alerts). These pre-configured alerts for Redis Database include:
1. Warning alert if usage of memory exceeds 60%
2. Alert will be triggered when memory usage exceeds 70%
If the alerting condition is met for these pre-configured alerts, some alert notifications may also be triggered.
Figure 12: A new alert being added that will be triggered when Redis used_cpu_user metric exceeds a threshold of <entered value> within a time period of 1 min
Alerts can also be configured against any of these 22 monitored metrics for Redis.
You can configure new alerts that will be triggered when performance issues with Redis arise. You can also configure the notification mechanisms for a triggered alert.
1. Go to Alerts Tab > Configure alerts and click on “New Alerts” button
2. Provide values for these fields in the New Alert page:
Uptime Cloud Monitor supports notifying different sets of users with differing notification mechanisms for each alert type. Notification mechanisms include:
Webhooks are also exposed for clients to configure custom notification mechanisms.
More about setting up website probe alerts can be found here.
Sign up for a 14 day FREE TRIAL of Uptime Cloud Monitor (no Credit Card required).
You can find more information about Uptime Cloud Monitor pricing options here.
We charge only $0.08 per month per metric!
Sign up today!