Monitoring with INFO command in Redis - Step-by-Step Execution

Concept Flow - Monitoring with INFO command

Start Redis Server

↓

Run INFO Command

↓

Redis Gathers Metrics

↓

Display Metrics Output

↓

Analyze Metrics for Monitoring

↓

End

The INFO command is run on a running Redis server to collect and display various server metrics for monitoring.

Execution Sample

Redis

redis-cli INFO

This command fetches detailed server statistics and information from the Redis server.

Execution Table

Step	Action	Command Output Sample	Result
1	Connect to Redis server	Connected to 127.0.0.1:6379	Ready to send commands
2	Send INFO command	INFO	Server starts gathering metrics
3	Receive INFO output	# Server redis_version:7.0.11 # Clients connected_clients:5 # Memory used_memory:1024000	Metrics displayed in sections
4	Analyze output	Check redis_version, connected_clients, used_memory	Use data for monitoring health
5	End session	QUIT	Disconnected from Redis server

💡 INFO command completes after sending all server metrics output

Variable Tracker

Variable	Start	After INFO command	Final
redis_version	N/A	7.0.11	7.0.11
connected_clients	N/A	5	5
used_memory	N/A	1024000	1024000

Key Moments - 2 Insights

Why does INFO output show multiple sections like Server, Clients, Memory?

INFO command organizes metrics into sections for clarity; see execution_table step 3 where output is grouped by categories.

Is the INFO command output live or cached?

INFO command fetches live metrics at the time of execution, so values like connected_clients reflect current state (execution_table step 3).

Visual Quiz - 3 Questions

Look at the execution table at step 3, what is the value of connected_clients?

A 7

B 5

C 1024000

D 127.0.0.1

💡 Hint

Check the 'Command Output Sample' column at step 3 for connected_clients value.

At which step does the Redis server start gathering metrics?

A Step 2

B Step 1

C Step 4

D Step 5

💡 Hint

Look at the 'Result' column to see when metrics gathering begins.

If the number of connected clients increases, which variable in variable_tracker changes?

A redis_version

B used_memory

C connected_clients

D N/A

💡 Hint

connected_clients tracks the number of active clients, see variable_tracker row for connected_clients.

Concept Snapshot

INFO command in Redis:
- Run 'redis-cli INFO' to get server stats
- Output grouped by sections: Server, Clients, Memory, etc.
- Shows live metrics like version, clients connected, memory used
- Useful for monitoring Redis health and performance
- Ends after printing all metrics

Full Transcript

To monitor Redis server health, you run the INFO command using redis-cli. This command connects to the Redis server and requests detailed metrics. The server gathers current data like version, number of connected clients, and memory usage. The output is organized into sections for easy reading. You analyze these metrics to understand server status. The session ends after the INFO output completes.

Practice

1. What does the Redis INFO command primarily provide?

easy

A. A snapshot of the Redis server status and statistics

B. A list of all keys stored in Redis

C. The configuration file contents

D. A backup of the Redis database

Solution

1. Step 1: Understand the purpose of INFO command

   The INFO command is designed to give a snapshot of the Redis server's current status and statistics.

2. Step 2: Compare with other options

   Listing keys, showing config files, or backups are done by other commands, not INFO.

3. Final Answer:

   A snapshot of the Redis server status and statistics -> Option A

4. Quick Check:

   INFO = Server status snapshot [OK]

Hint: INFO shows server stats, not keys or configs [OK]

Common Mistakes:

• Confusing INFO with commands like KEYS or CONFIG
• Thinking INFO returns data backups
• Assuming INFO lists all stored keys

2. Which of the following is the correct syntax to get only the memory section info from Redis?

easy

A. INFO --section=memory

B. INFO -memory

C. GET INFO memory

D. INFO memory

Solution

1. Step 1: Recall Redis INFO command syntax

   The correct syntax to get a specific section is INFO section_name, for example, INFO memory.

2. Step 2: Eliminate incorrect options

   Options with dashes or GET keyword are invalid Redis command syntax.

3. Final Answer:

   INFO memory -> Option D

4. Quick Check:

   INFO section_name = INFO memory [OK]

Hint: Use INFO followed by section name without dashes [OK]

Common Mistakes:

• Adding dashes before section name
• Using GET keyword with INFO
• Using double dashes or equal signs

3. Given the Redis INFO output snippet:

used_memory:1024000
connected_clients:5
uptime_in_seconds:3600

What does connected_clients indicate?

medium

A. Number of clients currently connected to Redis

B. Number of keys stored in Redis

C. Total memory used by Redis in bytes

D. Redis server uptime in seconds

Solution

1. Step 1: Identify the meaning of connected_clients

   The connected_clients field shows how many clients are currently connected to the Redis server.

2. Step 2: Differentiate from other fields

   used_memory is memory usage, uptime_in_seconds is server uptime, and keys count is not shown here.

3. Final Answer:

   Number of clients currently connected to Redis -> Option A

4. Quick Check:

   connected_clients = active connections [OK]

Hint: connected_clients means active users connected now [OK]

Common Mistakes:

• Confusing connected_clients with key count
• Mixing memory usage with client count
• Assuming uptime is client count

4. You run INFO client but get an error. What is the most likely cause?

medium

A. Redis server is down

B. You need to run INFO without any arguments

C. The section name 'client' is misspelled or unsupported

D. You must use GET instead of INFO

Solution

1. Step 1: Check valid section names for INFO

   Redis INFO supports specific section names like 'clients' (plural), not 'client' (singular).

2. Step 2: Understand error cause

   Using an invalid or misspelled section name causes an error, not server down or wrong command usage.

3. Final Answer:

   The section name 'client' is misspelled or unsupported -> Option C

4. Quick Check:

   INFO section names must be exact [OK]

Hint: Use exact section names; 'clients' not 'client' [OK]

Common Mistakes:

• Using singular instead of plural section names
• Assuming server is down without checking
• Trying GET command instead of INFO

5. You want to monitor Redis memory usage and client connections continuously. Which approach using the INFO command is best?

hard

A. Run INFO once and save output to a file

B. Run INFO memory and INFO clients repeatedly in a script with a delay

C. Use INFO all once and check manually later

D. Run CONFIG GET memory and CONFIG GET clients repeatedly

Solution

1. Step 1: Identify continuous monitoring needs

   To monitor memory and clients continuously, you need repeated INFO queries with a delay to track changes over time.

2. Step 2: Evaluate options

   Running INFO memory and INFO clients repeatedly in a script fits this need. Running once or using CONFIG GET won't provide continuous updates.

3. Final Answer:

   Run INFO memory and INFO clients repeatedly in a script with a delay -> Option B

4. Quick Check:

   Repeated INFO calls = continuous monitoring [OK]

Hint: Use repeated INFO calls in script for live monitoring [OK]

Common Mistakes:

• Running INFO only once for monitoring
• Using CONFIG GET which is for config, not stats
• Running INFO all once expecting continuous data