zabbix监控redis

1.Redis存活监控

redis存活监控 (redis_alive):redis本地监控agent使用ping，如果指定时间返回PONG表示存活，否则redis不能响应请求，可能阻塞或死亡。当返回值不为1时，redis挂了，告警，我们以阿里机器上的redis为例（集群部署）：

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

#下面指令我们就可以获取数字1，zabbix中就可以根据数字1或者0进行设置触发器

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

2.redis一些参数监控

这里我们不会很详细描述每一步操作，只是告诉如何去监控这些指标，实际情况根据自己的需要去监控，首先我们看看redis总管由那些指标

2.1 cluster info指令

[root@bfd-ango-01 ~]# redis-cli -h 47.105.115.143  -p 7000 -c  cluster info
cluster_state:ok
cluster_slots_assigned:16384
cluster_slots_ok:16384
cluster_slots_pfail:0
cluster_slots_fail:0
cluster_known_nodes:6
cluster_size:3
cluster_current_epoch:6
cluster_my_epoch:1
cluster_stats_messages_ping_sent:4085268
cluster_stats_messages_pong_sent:4113132
cluster_stats_messages_sent:8198400
cluster_stats_messages_ping_received:4113127
cluster_stats_messages_pong_received:4085266
cluster_stats_messages_meet_received:5
cluster_stats_messages_received:8198398

2.2 info指令

[root@bfd-ango-01 ~]# redis-cli -h 47.105.115.143  -p 7000 -c   info
#Server
redis_version:4.0.11
redis_git_sha1:00000000
redis_git_dirty:0
redis_build_id:3101afeef6330999
redis_mode:cluster
os:Linux 3.10.0-514.26.2.el7.x86_64 x86_64
arch_bits:64
multiplexing_api:epoll
atomicvar_api:atomic-builtin
gcc_version:4.8.5
process_id:2548154
run_id:30b9907b35131f375cd072eec7b92b2a5c29896c
tcp_port:7000
uptime_in_seconds:2230600
uptime_in_days:25
hz:10
lru_clock:3929725
executable:/opt/redis/conf/redis-server
config_file:/opt/redis/conf/redis7000.conf

# Clients
connected_clients:5
client_longest_output_list:0
client_biggest_input_buf:0
blocked_clients:0
 
# Memory
used_memory:2839336
used_memory_human:2.71M
used_memory_rss:5005312
used_memory_rss_human:4.77M
used_memory_peak:3045288
used_memory_peak_human:2.90M
used_memory_peak_perc:93.24%
used_memory_overhead:2642162
used_memory_startup:1444736
used_memory_dataset:197174
used_memory_dataset_perc:14.14%
total_system_memory:33568223232
total_system_memory_human:31.26G
used_memory_lua:37888
used_memory_lua_human:37.00K
maxmemory:0
maxmemory_human:0B
maxmemory_policy:noeviction
mem_fragmentation_ratio:1.76
mem_allocator:jemalloc-4.0.3
active_defrag_running:0
lazyfree_pending_objects:0
 
# Persistence
loading:0
rdb_changes_since_last_save:19
rdb_bgsave_in_progress:0
rdb_last_save_time:1547227619
rdb_last_bgsave_status:ok
rdb_last_bgsave_time_sec:0
rdb_current_bgsave_time_sec:-1
rdb_last_cow_size:237568
aof_enabled:1
aof_rewrite_in_progress:0
aof_rewrite_scheduled:0
aof_last_rewrite_time_sec:-1
aof_current_rewrite_time_sec:-1
aof_last_bgrewrite_status:ok
aof_last_write_status:ok
aof_last_cow_size:0
aof_current_size:338379
aof_base_size:0
aof_pending_rewrite:0
aof_buffer_length:0
aof_rewrite_buffer_length:0
aof_pending_bio_fsync:0
aof_delayed_fsync:0
 
# Stats
total_connections_received:253472
total_commands_processed:2479981
instantaneous_ops_per_sec:1
total_net_input_bytes:93456161
total_net_output_bytes:524528991
instantaneous_input_kbps:0.05
instantaneous_output_kbps:0.01
rejected_connections:0
sync_full:1
sync_partial_ok:0
sync_partial_err:1
expired_keys:253
expired_stale_perc:0.00
expired_time_cap_reached_count:0
evicted_keys:0
keyspace_hits:6425
keyspace_misses:157
pubsub_channels:0
pubsub_patterns:0
latest_fork_usec:278
migrate_cached_sockets:0
slave_expires_tracked_keys:0
active_defrag_hits:0
active_defrag_misses:0
active_defrag_key_hits:0
active_defrag_key_misses:0
 
# Replication
role:master
connected_slaves:1
slave0:ip=47.105.115.143,port=7005,state=online,offset=3445124,lag=0
master_replid:30b42c0552f22e68443b0eb703fa964deae5003a
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:3445124
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:2396549
repl_backlog_histlen:1048576
 
# CPU
used_cpu_sys:909.13
used_cpu_user:1279.84
used_cpu_sys_children:0.00
used_cpu_user_children:0.00
 
# Cluster
cluster_enabled:1
 
# Keyspace
db0:keys=170,expires=168,avg_ttl=6241746810

2.3 配置zabbix的redis_status.conf

到zabbix_agentd.d目录下，创建redis_status.conf文件，内容如下图所示
cd /etc/zabbix/zabbix_agentd.d

这是zabbix自定义监控，根据上面的内容可以看出，是根据脚本执行返回的结果进行监控，所以我们还要写shell脚本，脚本内容如下：

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}'

注意：上面图中下面还有一个redis_cluster_status.sh 其实里面的内容是一样的，只是一个命令是info，一个是clusetr info。其实这两个脚本可以合并为一个，传入参数即可,在zabbix监控mongodb这里就是传的两个参数。

3.zabbix监控

3.1 zabbix-get 工具检测

这时候一切都配置好了，我们重启zabbix_agent，例用之前安装的zabbix-get 工具进行检查一下，能够获取到值，则表示ok

[root@bfd-ango-01 shell]# zabbix_get -s 47.105.115.143 -k  redis.status[keyspace_misses]
157

3.2zabbix创建模板，并在模板中创建item和graph

3.2.1 配置item

3.2.2 配置graph

3.2.3 打开graph

**注意：

1. 这里其实根据数据量分成多个graph,因为有的值在0-100以内，有的值在几千到几万之间，所有的item都在一个图中，页面显示不友好，根据自己实际情况分成多个graph即可，这里只是演示作用。
2. 我们没有创建触发器，原因是这个是根据实际情况去配置，到一步后，后面也就简单了。**