summaryrefslogtreecommitdiffstats
path: root/iredis/data/commands/latency-graph.md
diff options
context:
space:
mode:
Diffstat (limited to 'iredis/data/commands/latency-graph.md')
-rw-r--r--iredis/data/commands/latency-graph.md46
1 files changed, 21 insertions, 25 deletions
diff --git a/iredis/data/commands/latency-graph.md b/iredis/data/commands/latency-graph.md
index ee3d93f..f1cfa5e 100644
--- a/iredis/data/commands/latency-graph.md
+++ b/iredis/data/commands/latency-graph.md
@@ -1,30 +1,26 @@
Produces an ASCII-art style graph for the specified event.
-`LATENCY GRAPH` lets you intuitively understand the latency trend of an `event`
-via state-of-the-art visualization. It can be used for quickly grasping the
-situation before resorting to means such parsing the raw data from
-`LATENCY HISTORY` or external tooling.
+`LATENCY GRAPH` lets you intuitively understand the latency trend of an `event` via state-of-the-art visualization. It can be used for quickly grasping the situation before resorting to means such parsing the raw data from `LATENCY HISTORY` or external tooling.
Valid values for `event` are:
+* `active-defrag-cycle`
+* `aof-fsync-always`
+* `aof-stat`
+* `aof-rewrite-diff-write`
+* `aof-rename`
+* `aof-write`
+* `aof-write-active-child`
+* `aof-write-alone`
+* `aof-write-pending-fsync`
+* `command`
+* `expire-cycle`
+* `eviction-cycle`
+* `eviction-del`
+* `fast-command`
+* `fork`
+* `rdb-unlink-temp-file`
-- `active-defrag-cycle`
-- `aof-fsync-always`
-- `aof-stat`
-- `aof-rewrite-diff-write`
-- `aof-rename`
-- `aof-write`
-- `aof-write-active-child`
-- `aof-write-alone`
-- `aof-write-pending-fsync`
-- `command`
-- `expire-cycle`
-- `eviction-cycle`
-- `eviction-del`
-- `fast-command`
-- `fork`
-- `rdb-unlink-temp-file`
-
-@example
+@examples
```
127.0.0.1:6379> latency reset command
@@ -56,8 +52,8 @@ The vertical labels under each graph column represent the amount of seconds,
minutes, hours or days ago the event happened. For example "15s" means that the
first graphed event happened 15 seconds ago.
-The graph is normalized in the min-max scale so that the zero (the underscore in
-the lower row) is the minimum, and a # in the higher row is the maximum.
+The graph is normalized in the min-max scale so that the zero (the underscore
+in the lower row) is the minimum, and a # in the higher row is the maximum.
For more information refer to the [Latency Monitoring Framework page][lm].
@@ -65,4 +61,4 @@ For more information refer to the [Latency Monitoring Framework page][lm].
@return
-@bulk-string-reply
+@bulk-string-reply \ No newline at end of file