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-reset.md | 36 +++++++++++++++++++++++++++++++++++ 1 file changed, 36 insertions(+) create mode 100644 iredis/data/commands/latency-reset.md (limited to 'iredis/data/commands/latency-reset.md') 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. -- cgit v1.2.3