Latency monitoring in Redis - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to enable latency monitoring in Redis.

Redis

redis-cli CONFIG SET [1] 100

Drag options to blanks, or click blank then click option'

Alatency-monitor-threshold

Bmaxmemory

Ctimeout

Dsave

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'maxmemory' instead of latency setting.

Confusing 'timeout' with latency threshold.

The 'latency-monitor-threshold' config sets the minimum latency in milliseconds to log events.

2fill in blank

medium

Complete the command to check the latency events recorded by Redis.

Redis

redis-cli [1] LATENCY LATEST

Drag options to blanks, or click blank then click option'

AMONITOR

BINFO

CLATENCY

DCONFIG

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'MONITOR' which streams all commands but not latency summary.

Using 'INFO' which shows general stats but not detailed latency.

The 'LATENCY LATEST' command shows the latest latency events recorded by Redis.

3fill in blank

hard

Fix the error in the command to reset latency data.

Redis

redis-cli LATENCY [1]

Drag options to blanks, or click blank then click option'

ARESET

BCLEAR

CDELETE

DREMOVE

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'CLEAR' which is not a valid subcommand.

Using 'DELETE' or 'REMOVE' which do not exist for latency.

The correct subcommand to reset latency data is 'RESET'.

4fill in blank

hard

Fill both blanks to reset latency data for a specific command.

Redis

redis-cli LATENCY [1] [2]

Drag options to blanks, or click blank then click option'

AADD

BRESET

CGET

DSET

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'ADD' which does not exist for latency.

Using 'GET' instead of 'SET' as the command name.

The 'RESET' subcommand resets the latency data for the 'SET' command.

5fill in blank

hard

Fill all three blanks to list latency events and reset a specific command's latency data.

Redis

redis-cli LATENCY [1] && redis-cli LATENCY [2] [3]

Drag options to blanks, or click blank then click option'

ALATEST

BRESET

CSET

DDOCTOR

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'DOCTOR' instead of 'LATEST' to list events.

Using wrong command name instead of 'SET' for reset.

The first command lists latest latency events, the second resets latency data for the 'SET' command.