Azure Redis Enterprise E10 reports: ERR TSDB: the key does not exist

Good evening!

In Azure I have created a Redis Cache “Enterprise E10” instance with RedisTimeSeries module activated:

And then I connect to it using the “redis-cli” running at my Macbook:

$ redis-cli -c -h XXX.westeurope.redisenterprise.cache.azure.net -p 10000 -a XXX
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
XXX.westeurope.redisenterprise.cache.azure.net:10000> TS.INFO me_metric
-> Redirected to slot [15141] located at 20.73.XXX.XXX:8503
(error) ERR TSDB: the key does not exist
20.73.XXX.XXX:8503> TS.ADD my_metric * 25
-> Redirected to slot [5926] located at 20.73.XXX.XXX:8500
(integer) 1692721273270
20.73.XXX.XXX:8500> TS.ADD my_metric * 25
(integer) 1692721276153
20.73.XXX.XXX:8500> TS.INFO me_metric
-> Redirected to slot [15141] located at 20.73.XXX.XXX:8503
(error) ERR TSDB: the key does not exist

Does anybody please have an explanation, why is “me_metric” not found?

Below I have pasted the INFO command output

Greetings from Germany
Alex

# Server
redis_version:6.0.17
redis_git_sha1:00000000
redis_git_dirty:0
redis_build_id:0000000000000000000000000000000000000000
redis_mode:standalone
os:Linux 5.4.0-1107-azure x86_64
arch_bits:64
multiplexing_api:epoll
gcc_version:7.5.0
process_id:1
run_id:631f9b064b15c313d9f9469aa7080ca6fc5876eb
tcp_port:10000
server_time_usec:1692721014000000
uptime_in_seconds:114138
uptime_in_days:1
hz:10
lru_clock:0
config_file:

# Clients
connected_clients:12
client_longest_output_list:0
client_biggest_input_buf:0
blocked_clients:0
maxclients:0
cluster_connections:0

# Memory
used_memory:556158240
used_memory_human:530.39M
used_memory_rss:556158240
used_memory_peak:560656528
used_memory_peak_human:534.68M
used_memory_lua:368640
mem_fragmentation_ratio:1
mem_allocator:jemalloc-5.2.1

# Persistence
loading:0
rdb_changes_since_last_save:0
rdb_bgsave_in_progress:0
rdb_last_save_time:1692682924
rdb_last_bgsave_status:ok
rdb_last_bgsave_time_sec:0
rdb_current_bgsave_time_sec:-1
aof_enabled:0
aof_rewrite_in_progress:0
aof_rewrite_scheduled:0
aof_last_rewrite_time_sec:-1
aof_current_rewrite_time_sec:-1
aof_last_bgrewrite_status:ok
aof_last_write_status:ok

# Stats
total_connections_received:1414146
total_commands_processed:38
instantaneous_ops_per_sec:24
total_net_input_bytes:47558229
total_net_output_bytes:283621017
instantaneous_input_kbps:1.22
instantaneous_output_kbps:6.90
rejected_connections:0
sync_full:0
sync_partial_ok:0
sync_partial_err:0
expired_keys:0
evicted_keys:0
keyspace_hits:0
keyspace_misses:0
pubsub_channels:0
pubsub_patterns:0
latest_fork_usec:0
migrate_cached_sockets:0
total_forks:0
total_error_replies:0

# Replication
role:master
connected_slaves:1
slave0:ip=0.0.0.0,port=0,state=online,offset=0,lag=0
master_repl_offset:0
repl_backlog_active:0
repl_backlog_size:1048576
repl_backlog_first_byte_offset:0
repl_backlog_histlen:0

# CPU
used_cpu_sys:0.00
used_cpu_user:0.00
used_cpu_sys_children:0.00
used_cpu_user_children:0.00
used_cpu_sys_main_thread:0.00
used_cpu_user_main_thread:0.00

# Cluster
cluster_enabled:1

# Keyspace
db0:keys=3,expires=0,avg_ttl=0

IT seems you only created timeseries named my_metric and not me_metric,
Here you created the series:

It might be a typo: me_metric != my_metric

1 Like

Thank you for spotting my typo! :sweat_smile: