Skip to main content
Use CONFIG GET to read runtime configuration parameters. Parameter names may contain glob-style patterns, so one call can fetch a family of settings, and the reply is a flat array of alternating names and values in both RESP2 and RESP3. This deployment exposes only notify-keyspace-events, which controls the keyspace notifications published on pub/sub. Other names simply return no matching entries rather than an error, so check the reply for the parameter you asked about instead of assuming it was present.

Syntax

Arguments

Important points

  • This command can expose administrative information or make a broad destructive change. Restrict it to trusted code paths.
  • This deployment exposes only notify-keyspace-events. Other patterns return no matching entries.
  • Both RESP2 and RESP3 return a flat array of alternating parameter names and values.

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.
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.
This command is not supported yet in @upstash/redis.
This command is not supported yet in upstash_redis.