From 06cba6ccd165ca8b224797e37fccb9e63f026d77 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 21 Mar 2020 11:28:17 +0100 Subject: Adding upstream version 1.9.1. Signed-off-by: Daniel Baumann --- iredis/data/commands/latency-latest.md | 38 ++++++++++++++++++++++++++++++++++ 1 file changed, 38 insertions(+) create mode 100644 iredis/data/commands/latency-latest.md (limited to 'iredis/data/commands/latency-latest.md') diff --git a/iredis/data/commands/latency-latest.md b/iredis/data/commands/latency-latest.md new file mode 100644 index 0000000..883f0a5 --- /dev/null +++ b/iredis/data/commands/latency-latest.md @@ -0,0 +1,38 @@ +The `LATENCY LATEST` command reports the latest latency events logged. + +Each reported event has the following fields: + +- Event name. +- Unix timestamp of the latest latency spike for the event. +- Latest event latency in millisecond. +- All-time maximum latency for this event. + +"All-time" means the maximum latency since the Redis instance was started, or +the time that events were reset `LATENCY RESET`. + +@example: + +``` +127.0.0.1:6379> debug sleep 1 +OK +(1.00s) +127.0.0.1:6379> debug sleep .25 +OK +127.0.0.1:6379> latency latest +1) 1) "command" + 2) (integer) 1405067976 + 3) (integer) 251 + 4) (integer) 1001 +``` + +For more information refer to the [Latency Monitoring Framework page][lm]. + +[lm]: /topics/latency-monitor + +@return + +@array-reply: specifically: + +The command returns an array where each element is a four elements array +representing the event's name, timestamp, latest and all-time latency +measurements. -- cgit v1.2.3