Use CONFIG GET to read runtime configuration parameters.
Parameter names may contain glob-style patterns, so one call can fetch a family of settings. The reply is a map of names to values under RESP3, and the same pairs as a flat array under RESP2.
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#
| Argument | Required | Repeatable | Description |
|---|---|---|---|
parameter | Yes | Yes | One or more glob-style configuration parameter patterns. |
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.
| Protocol | Reply |
|---|---|
| RESP2 | Flat array of alternating configuration names and values |
| RESP3 | Map of configuration names to values |
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
@upstash/redis
This command is not supported yet in @upstash/redis.
upstash_redis
This command is not supported yet in upstash_redis.