LATENCY-HISTORY(3valkey)

✨ LATENCY-HISTORY ✨</p> — the valkey manual, but make it cute 💅

okay bestie, sit down, hydrate, and let's talk about latency-history from the valkey command manual (section 3, iykyk). she returns timestamp-latency samples for an event. that's it. that's the girl. 🎀

---

🌸 NAME 🌸

latency-history — Returns timestamp-latency samples for an event.

---

🦋 SYNOPSIS 🦋

LATENCY HISTORY event

---

💖 DESCRIPTION 💖

so basically, LATENCY HISTORY hands you the raw data of the event's latency spikes time series. no filter, no glow-up, just the receipts. 🔥

this is lowkey perfect for an app that wants to pull raw data so it can do monitoring, display graphs, and so forth. main character data-collection energy, fr fr.

the command will return up to 160 timestamp-latency pairs for the event. not 161. 160. periodt. 💅

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

---

🌈 REPLY 🌈

valkey-protocol(7) Array reply: an array where each element is a two elements array representing the timestamp and the latency of the event. so it's arrays inside arrays, nested-core, absolutely giving russian doll but make it observability. 🪆✨

---

⭐ COMPLEXITY ⭐

O(1)

she's fast. she's efficient. she's not doing the most. 👑

---

🔐 ACL CATEGORIES 🔐

@admin @dangerous @slow

ok so heads up bestie: @admin + @dangerous means you probably shouldn't be letting just anyone run this, and @slow is right there in the name. be careful who you hand the keys to. 🙈

---

💜 HISTORY 💜

• Available since: 2.8.13

---

🎀 EXAMPLES 🎀

127.0.0.1:6379> latency history command
1) 1) (integer) 1405067822
   2) (integer) 251
2) 1) (integer) 1405067941
   2) (integer) 1001

For more information refer to the Latency Monitoring Framework page.

---

🫶 SEE ALSO 🫶

acl(3valkey), acl-cat(3valkey), acl-deluser(3valkey), acl-dryrun(3valkey), acl-genpass(3valkey), acl-getuser(3valkey), acl-help(3valkey), acl-list(3valkey), acl-load(3valkey), acl-log(3valkey), acl-save(3valkey), acl-setuser(3valkey), acl-users(3valkey), acl-whoami(3valkey), bgrewriteaof(3valkey), bgsave(3valkey), command(3valkey), command-count(3valkey), command-docs(3valkey), command-getkeys(3valkey), command-getkeysandflags(3valkey), command-help(3valkey), command-info(3valkey), command-list(3valkey), commandlog(3valkey), commandlog-get(3valkey), commandlog-help(3valkey), commandlog-len(3valkey), commandlog-reset(3valkey), config(3valkey), config-get(3valkey), config-help(3valkey), config-resetstat(3valkey), config-rewrite(3valkey), config-set(3valkey), dbsize(3valkey), debug(3valkey), failover(3valkey), flushall(3valkey), flushdb(3valkey), info(3valkey), lastsave(3valkey), latency(3valkey), latency-doctor(3valkey), latency-graph(3valkey), latency-help(3valkey), latency-histogram(3valkey), latency-latest(3valkey), latency-reset(3valkey), lolwut(3valkey), memory(3valkey), memory-doctor(3valkey), memory-help(3valkey), memory-malloc-stats(3valkey), memory-purge(3valkey), memory-stats(3valkey), memory-usage(3valkey), module(3valkey), module-help(3valkey), module-list(3valkey), module-load(3valkey), module-loadex(3valkey), module-unload(3valkey), monitor(3valkey), psync(3valkey), replconf(3valkey), replicaof(3valkey), restore-asking(3valkey), role(3valkey), save(3valkey), shutdown(3valkey), slowlog(3valkey), slowlog-get(3valkey), slowlog-help(3valkey), slowlog-len(3valkey), slowlog-reset(3valkey), swapdb(3valkey), sync(3valkey), time(3valkey)

---

ok that's the whole page, you ate that 💅 this was valkey version 9.0.0, dated 2025-10-21, and that's the vibe check, bestie — go read your latency data and slay. 💖✨🦋