Slow log threshold

See the slow-log threshold and change it through a reviewed CONFIG SET.

On Redis connections the Activity Monitor's Expensive Queries tab is the server's slow log (SLOWLOG GET). Above the table, SQLly reads and shows the threshold that decides what gets logged - slowlog-log-slower-than, in microseconds - so you know whether an empty table means a fast server or a threshold set too high. Any negative value (Redis stops logging for all of them, not only -1) is shown as "Slow log disabled".

Changing the threshold

Type a new value in microseconds (10000 is 10 ms; 0 logs every command; -1 disables the log) and press Change Threshold…. Nothing runs yet: SQLly shows the exact statement - CONFIG SET slowlog-log-slower-than 10000 - for review, and only Run executes it. The threshold is read back afterwards, so the row always shows what the server actually has.

CONFIG SET changes the running server only. To keep the change after a restart, use Persist (CONFIG REWRITE)…, which is reviewed the same way. It writes every runtime configuration change into the server's config file, and fails on servers started without one.

SQLly

The statements run through the connection's guardrails, so a read-only connection refuses them with its reason. On a production connection whose writes are locked, Change Threshold…, Persist and Run are disabled until you unlock writes from the status-bar chip. The lock is checked again right before a reviewed statement runs. An ACL user needs +config to read or change the threshold. When the read fails, the row shows the server's reason: a missing permission, or a CONFIG command that is disabled or renamed (common on managed Redis).