redis monitoring of zabbix

Disclaimer: This article is a blogger original article, shall not be reproduced without the bloggers allowed. https://blog.csdn.net/wyl9527/article/details/90599950

Redis alive monitoring

redis alive monitoring (redis_alive): redis local monitoring agent using ping, if the specified time to return PONG represent survival, or redis not respond to the request, may block or death. When the return value is not 1, Redis hung up, alarm

[root@bfd-ango-01 zabbix_agentd.d]# redis-cli -h 47.105.115.143 -p 7000 -c ping | grep -c PONG 1 [root@bfd-ango-01 zabbix_agentd.d]# redis-cli -h 47.105.115.143 -p 7000 -c ping PONG

Number of client connections

 

The number of connections (connected_clients): number of client connections, if the number of connections is affected by high throughput redis. > 5000 Alarm

redis-cli -h 47.105.115.143 -p 7000 -c info |grep -w "connected_clients" | awk -F":" '{print $2}' 5

 

Redis

redis.cluster.status[cluster_known_nodes]

The number of nodes in the cluster redis: the cluster nodes (cluster_known_nodes)

redis.cluster.status[cluster_slots_fail]

Detecting the number of data slots groove offline (cluster_slots_fail): cluster normal operation, it should be greater than 0 to 0. If the cluster has faulty slot Description

redis.cluster.status[cluster_slots_ok]

Cluster data slot allocation slots (cluster_slots_assigned): cluster normal operation, the default slots 16384

redis.status.clusterOK

Cluster health status (clusster_state): cluster_state the alarm is not OK

redis.status.ping

PONG represents survival, or redis not respond to the request, may block or death. If the return value is not 1, Redis hung up, alarm

redis.status.server

redis-server service number

redis.status[cluster_enabled]

Cluster mode is enabled by cluster_enabled monitoring the info. It is not equal to an alarm

redis.status[connected_clients]

Client connection number, if the number of connections is affected by high throughput redis.

redis.status[keyspace_hits]

Request key is hit frequency (keyspace_hits): redis request key is hit times

redis.status[keyspace_misses]

Request key is not the number of hits (keyspace_misses): redis request key is not the number of hits

redis.status[rejected_connections]

The number of rejected connection (rejected_connections): redis limit the number of connected maxclients reached, the number of new connection refused. Warning

redis.status[total_commands_processed]

Redis number of commands processed (total_commands_processed): monitoring the average acquisition cycle qps

redis.status[total_connections_received]

If the newly created too many connections, create and destroy excessive connection performance impact, indicating serious short connection or a problem with the use of the pool, alarm.

redis.status[used_memory]

redis allocated memory size (used_memory): redis real use of memory, memory fragmentation is not included

 

[root@bfd-ango-01 zabbix_agentd.d]# cat redis_status.conf UserParameter=redis.status.server,ps -ef |grep redis-server|grep -v grep|wc -l UserParameter=redis.status.clusterOK,/opt/redis/bin/redis-cli -c -p 7000 cluster info|grep -c cluster_state:ok UserParameter=redis.status.ping,/opt/redis/bin/redis-cli -c -p 7000 ping | grep -c PONG UserParameter=redis.status[*],/usr/bin/sh /etc/zabbix/shell/redis_status.sh $1 UserParameter=redis.cluster.status[*],/usr/bin/sh /etc/zabbix/shell/redis_cluster_status.sh $1
[root@bfd-ango-01 shell]# cat redis_status.sh redisCli=/opt/redis/bin/redis-cli host=47.105.115.143 port=7000 ${redisCli} -h ${host} -p ${port} -c info |grep -w $1|awk -F ':' '{print $2}'



[root@bfd-ango-01 shell]# cat redis_cluster_status.sh redisCli=/opt/redis/bin/redis-cli host=47.105.115.143 port=7000 ${redisCli} -h ${host} -p ${port} -c cluster info |grep -w $1|awk -F ':' '{print $2}'

zabbix monitoring, there is no longer added.

Guess you like

Origin blog.csdn.net/wyl9527/article/details/90599950