How Does eG Enterprise Monitor Redis OSS Cluster?

eG Enterprise uses a single eG external agent to monitor the target Redis OSS Cluster. The external agent can be deployed on any remote host in the environment.

In this approach, an external agent deployed on the remote host periodically runs Redis commands on the cluster to pull the metrics of interest from across the nodes in the cluster. This way, eG Enterprise enables administrators to promptly detect performance issues on the cluster and resolve them, so that user experience with the server is not affected.

Pre-requisites for Monitoring the Redis OSS Cluster

• If the Redis OSS Cluster is deployed behind the firewall, make sure that the firewall is configured to allow the eG agent  to communicate with all the nodes in the cluster and collect metrics on cluster availability, server connectivity, replication/clustering performance, failover, node status, etc.

• If the target cluster component is Redis v6 or above then, to execute the tests of the Redis OSS Cluster component, the eG agent should be configured with the credentials of a user who has Read-only privileges on the monitored Redis Cluster Server. If such a user does not pre-exist, then, you need to manually create a user account with the aforesaid privileges on every cluster nodes that requires monitoring. To create and configure such a user, run the following command:

  acl setuser <username> on ><passowrd> allcommands allkeys

  For example, to create an eguser with read only privilege run the following command:acl setuser eguser allkeys -@all +client|list +cluster|info +cluster|nodes +config|get +info +memory|usage +ping +scan +slowlog|get +time +ttl +xinfo|groups +xinfo|stream resetchannels on >password