summaryrefslogtreecommitdiffstats
path: root/iredis/data/commands/latency-reset.md
diff options
context:
space:
mode:
Diffstat (limited to 'iredis/data/commands/latency-reset.md')
-rw-r--r--iredis/data/commands/latency-reset.md36
1 files changed, 36 insertions, 0 deletions
diff --git a/iredis/data/commands/latency-reset.md b/iredis/data/commands/latency-reset.md
new file mode 100644
index 0000000..cec6f06
--- /dev/null
+++ b/iredis/data/commands/latency-reset.md
@@ -0,0 +1,36 @@
+The `LATENCY RESET` command resets the latency spikes time series of all, or
+only some, events.
+
+When the command is called without arguments, it resets all the events,
+discarding the currently logged latency spike events, and resetting the maximum
+event time register.
+
+It is possible to reset only specific events by providing the `event` names as
+arguments.
+
+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`
+
+For more information refer to the [Latency Monitoring Framework page][lm].
+
+[lm]: /topics/latency-monitor
+
+@reply
+
+@integer-reply: the number of event time series that were reset.