INFO - Upstash Documentation

Use INFO to get statistics and information about the server.

The reply groups fields into sections such as server, clients, memory, stats, replication, and keyspace, and passing a section name limits the reply to that one. It is the usual source for operational numbers such as connected clients, memory in use, hit and miss counts, and the number of keys per database.

On Upstash, default and all return the same set of sections, and a section name that is not supported produces only its heading. The reply is a CRLF-delimited text report rather than a RESP map, so parse it defensively, since fields may be added over time.

Syntax#

INFO [section]

Arguments#

Argument	Required	Repeatable	Description
`section`	No	No	Section to return: `server`, `clients`, `memory`, `stats`, `cluster`, `keyspace`, `default`, or `all`.

Important points#

This command can expose administrative information or make a broad destructive change. Restrict it to trusted code paths.
default and all return the same Upstash section set. Unsupported section names produce only a section heading.
The reply is a CRLF-delimited text report, not a RESP map. Parse it defensively because fields may be added over time.

Response#

The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.

Protocol	Reply
RESP2	Bulk string
RESP3	Bulk string

Note

Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.

Examples#

TCP examples use the TLS REDIS_URL from the Upstash console. REST examples use UPSTASH_REDIS_REST_URL and UPSTASH_REDIS_REST_TOKEN.

Redis CLI

INFO memory

@upstash/redis

Note

This command is not supported yet in @upstash/redis.

upstash_redis

Note

This command is not supported yet in upstash_redis.

ioredis

import Redis from "ioredis";const redis = new Redis(process.env.REDIS_URL!);const result = await redis.info("memory");console.log(result);

node-redis

import { createClient } from "redis";const client = await createClient({ url: process.env.REDIS_URL })  .on("error", console.error)  .connect();const result = await client.info("memory");console.log(result);

redis-py

import osimport redisclient = redis.from_url(os.environ["REDIS_URL"])result = client.info("memory")print(result)

go-redis

package mainimport (    "context"    "fmt"    "os"    "github.com/redis/go-redis/v9")func main() {    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))    if err != nil {        panic(err)    }    client := redis.NewClient(opts)    result, err := client.Info(context.Background(), "memory").Result()    if err != nil {        panic(err)    }    fmt.Println(result)}

jedis

import java.net.URI;import redis.clients.jedis.Jedis;try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {  Object result = jedis.info("memory");  System.out.println(result);}

redis-rs

fn main() -> redis::RedisResult<()> {    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");    let client = redis::Client::open(url)?;    let mut connection = client.get_connection()?;    let mut command = redis::cmd("INFO");    command.arg("memory");    let result: redis::Value = command.query(&mut connection)?;    println!("{result:?}");    Ok(())}