Redis Performance Metrics monitoring commands

Source: Internet
Author: User


Redis Performance Metrics monitoring commands


In the process of learning, we must learn to use help frequently to understand the specific use of commands.


1.info (monitoring typically uses this command to read data)

127.0.0.1:6379> Help Info


INFO [Section]

Summary:get information and statistics about the server

since:1.0.0

Group:server


127.0.0.1:6379> Info

# Server

redis_version:3.0.7

redis_git_sha1:00000000

redis_git_dirty:0

Redis_build_id:8d64350b19f2f7d2

Redis_mode:standalone

Os:linux 2.6.32-504.el6.x86_64 x86_64

Arch_bits:64

Multiplexing_api:epoll

gcc_version:4.4.7

process_id:1096

run_id:2fc6a6e9638de4b9bccce3def6b40bb7b69e5240

tcp_port:6379

uptime_in_seconds:1668

uptime_in_days:0

Hz:10

lru_clock:3766532

Config_file:/etc/redis/6379.conf


# clients

Connected_clients:3

client_longest_output_list:0

client_biggest_input_buf:0

blocked_clients:0


# Memory

used_memory:856928

used_memory_human:836.84k

used_memory_rss:3223552

used_memory_peak:856968

used_memory_peak_human:836.88k

used_memory_lua:36864

mem_fragmentation_ratio:3.76

mem_allocator:jemalloc-3.6.0


# persistence

loading:0

rdb_changes_since_last_save:0

rdb_bgsave_in_progress:0

rdb_last_save_time:1480159872

Rdb_last_bgsave_status:ok

Rdb_last_bgsave_time_sec:-1

Rdb_current_bgsave_time_sec:-1

aof_enabled:0

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


# Stats

Total_connections_received:2

total_commands_processed:189

instantaneous_ops_per_sec:0

total_net_input_bytes:3340

total_net_output_bytes:66405

instantaneous_input_kbps:0.00

instantaneous_output_kbps:0.04

rejected_connections:0

sync_full:0

sync_partial_ok:0

sync_partial_err:0

expired_keys:0

evicted_keys:0

keyspace_hits:0

keyspace_misses:0

pubsub_channels:0

pubsub_patterns:0

latest_fork_usec:0

migrate_cached_sockets:0


# Replication

Role:slave

master_host:192.168.1.93

master_port:6380

Master_link_status:up

Master_last_io_seconds_ago:9

master_sync_in_progress:0

slave_repl_offset:2283

slave_priority:100

Slave_read_only:1

connected_slaves:0

master_repl_offset:0

repl_backlog_active:0

repl_backlog_size:1048576

repl_backlog_first_byte_offset:0

repl_backlog_histlen:0


# CPU

used_cpu_sys:0.97

used_cpu_user:0.42

used_cpu_sys_children:0.00

used_cpu_user_children:0.00


# Cluster

cluster_enabled:0


# Keyspace

Db0:keys=1,expires=0,avg_ttl=0



2.monitor (affects performance, use sparingly)

127.0.0.1:6379> Help Monitor


MONITOR-

Summary:listen for all requests received by the server in real time

since:1.0.0

Group:server

127.0.0.1:6379> Monitor

Ok

1480161369.716981 [0 192.168.1.93:6380] "PING"

1480161379.816223 [0 192.168.1.93:6380] "PING"

1480161389.930811 [0 192.168.1.93:6380] "PING"

1480161400.047882 [0 192.168.1.93:6380] "PING"

1480161409.461477 [0 127.0.0.1:42333] "info"

1480161410.143357 [0 192.168.1.93:6380] "PING"

1480161420.267618 [0 192.168.1.93:6380] "PING"

1480161421.141619 [0 127.0.0.1:42333] "info" "All"

1480161430.367934 [0 192.168.1.93:6380] "PING"

1480161440.496221 [0 192.168.1.93:6380] "PING"



3.slowlog

127.0.0.1:6379> Help Slowlog


SLOWLOG subcommand [argument]

Summary:manages the Redis slow queries log

since:2.2.12

Group:server


127.0.0.1:6379> Slowlog Get

1) 1) (integer) 17

2) (integer) 1480161791

3) (integer) 12

4) 1) "Config"

2) "Set"

3) "Slowlog-log-slower-than"

4) "10"

127.0.0.1:6379> Slowlog Len

(integer) 2


This article is from the "dba003" blog, make sure to keep this source http://dba003.blog.51cto.com/12318731/1877617

Redis performance Metrics monitoring commands

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.