SLOWLOG-GET(3valkey)

📦
version 9.0.6 · 2 versions
, in fedora 44

💅 NAME 💅

okay so bestie, this is slowlog-get — and it returns the slow log's entries. that's the whole vibe. it's the Valkey Command Manual entry for SLOWLOG-GET(3valkey), and yes it's giving very "let me show u receipts" energy. 🧾✨

🌸 SYNOPSIS 🌸

SLOWLOG GET [count]

that's it. that's the whole thing. iconic. 👑

✨ DESCRIPTION ✨

okay so SLOWLOG GET hands you back entries from the slow log, and it does it in chronological order — like, oldest first, in the order they actually happened. no shuffling, no chaos. 🕰️

now let's talk about what the Valkey Slow Log even is. it's a whole system for logging queries that went over a specified execution time. and here's the part ppl always get wrong: that execution time does not include I/O operations — not talking with the client, not sending the reply, none of that. it's just the time needed to actually execute the command. which makes sense actually, because that's the only stage of command execution where the thread is blocked and can't serve other requests in the meantime. so yeah, that's the number that actually matters. 🫶

a new entry gets added to the slow log whenever a command exceeds the execution time threshold defined by the slowlog-log-slower-than configuration directive. and the maximum number of entries the slow log can hold? that's governed by the slowlog-max-len configuration directive. two configs, two jobs, both slaying. 💖

by default the command returns the latest ten entries in the log. the optional count argument limits how many come back, so the command returns at most up to count entries. and the special number -1 means return all entries. (yes, -1 is the "give me everything, idc" option. we love her.) 🙈

each entry from the slow log is made up of these six values:

  1. a unique progressive identifier for every slow log entry.
  2. the unix timestamp at which the logged command was processed.
  3. the amount of time needed for its execution, in microseconds.
  4. the array composing the arguments of the command.
  5. client IP address and port.
  6. client name if set via the CLIENT SETNAME command.

and the entry's unique ID? it exists so you can avoid processing slow log entries multiple times — like, say you've got a script emailing you an alert for every new slow log entry. that ID is your bestie fr fr. 🥹 important: the ID is never reset in the course of the Valkey server execution. only a server restart will reset it.

🦋 Alternative 🦋

COMMANDLOG GET <count> SLOW

(that's the other way to get the same energy, iykyk.)

💜 REPLY 💜

valkey-protocol(7) Array reply: a list of slow log entries per the above format. 💫

🔥 COMPLEXITY 🔥

O(N) where N is the number of entries returned. not me stressing over the letters, it's fine, it's linear. 🫠

👑 ACL CATEGORIES 👑

@admin @dangerous @slow

heads up bestie: @dangerous is right there in the list. this one is not a casual little command. treat it accordingly. 💀

🌈 HISTORY 🌈

  • Available since: 2.2.12
  • Changed in 4.0.0: Added client IP address, port and name to the reply.

🎀 SEE ALSO 🎀

the whole extended family showed up, and we're listing every single one because nobody gets left out:

and that's the whole page, bestie!! 💖✨ this was version 9.0.0, dated 2025-10-21, straight from the Valkey Command Manual for SLOWLOG-GET(3valkey). go log something slow and slay. 🦋🎀

📦 where this page comes from