Configuration of RedisCpuTest
This test monitors the CPU usage of the Redis server and alerts administrators to erratic usage patterns on the server and what is causing them. This way, the test helps administrators isolate and pre-empt CPU contentions on the server, and thus improve server performance.
The default parameters associated with this test are:
-
In some high security environments, a password may have been set for the Redis server, so as to protect it from unauthorized accesses/abuse. If such a password has been set for the monitored Redis server, then specify that password against REDIS PASSWORD. Then, confirm the password by retyping it against CONFIRM PASSWORD.
If the Redis server is not password protected, then do not disturb the default setting of this parameter.
To determine whether/not the target Redis server is password-protected, do the following:
- Login to the system hosting the Redis server.
- Open the redis.conf file in the <REDIS_INSTALL_DIR>.
- Look for the requirepass parameter in the file.
- If this parameter exists, and is not preceded by a # (hash) symbol, it means that password protection is enabled for the Redis server. In this case, the string that follows the requirepass parameter is the password of the Redis server. For instance, say that the requirepass specification reads as follows:
requirepass red1spr0
According to this specification, the Redis server is protected using the password red1spr0. In this case therefore, you need to specify red1spr0 against REDIS PASSWORD.
- On the other hand, if the requirepass parameter is prefixed by the # (hash) symbol as shown below, it means password protection is disabled.
# requirepass red1spr0
In this case, leave the REDIS PASSWORD parameter with its default setting.
When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz*” and $port will be changed to “80” when configuring a test.
|