Not pulling data??!

[Matt Westfall]

https://ss.ecansol.com/uploads/2026/04/23/chrome_2026-04-23_21-36-25.png

So I noticed on the dashboard, the amount of ‘data’ was very low considering there’s about 2 Gbps of traffic throwing through devices aggregate, so I started clicking around and as you can see above, it doesn’t seem to be pulling any data from this device, and/or not saving / displaying it, however you want to look at it.

I’m gonna reboot the VM see if data comes back, but bigger question, why did it stop?

[Matt Westfall]

Getting all this too:

[code]
Received syslog message from 172.16.200.25: script,error mikrowizard15: executing script RWBHEALTHCHECK from scheduler (RWBHEALTHCHECK) failed, please check it manually
script,error mikrowizard15: executing script RWBHEALTHCHECK from scheduler (RWBHEALTHCHECK) failed, please check it manually
Received syslog message from 172.16.200.25: script,error,debug mikrowizard15: no such item (/interface/get; line 1)
Received syslog message from 172.16.200.10: system,info,account mikrowizard1: user admin logged in from 172.16.200.1 via api
PROD ERR [email protected].0.1 240426-02:02:24 red.py TSDB: the key does not exist
PROD ERR [email protected].0.1 240426-02:02:24 red.py TSDB: the key does not exist
PROD ERR [email protected].0.1 240426-02:02:24 red.py TSDB: the key does not exist
PROD ERR [email protected].0.1 240426-02:02:24 red.py TSDB: the key does not exist
PROD ERR [email protected].0.1 240426-02:02:24 red.py TSDB: the key does not exist
PROD ERR [email protected].0.1 240426-02:02:24 red.py TSDB: the key does not exist
PROD ERR [email protected].0.1 240426-02:02:24 red.py TSDB: the key does not exist
PROD ERR [email protected].0.1 240426-02:02:24 red.py TSDB: the key does not exist
PROD ERR [email protected].0.1 240426-02:02:24 red.py TSDB: the key does not exist
PROD ERR [email protected].0.1 240426-02:02:24 red.py TSDB: the key does not exist
PROD ERR [email protected].0.1 240426-02:02:24 red.py TSDB: the key does not exist
PROD ERR [email protected].0.1 240426-02:02:24 red.py TSDB: the key does not exist
PROD ERR [email protected].0.1 240426-02:02:24 red.py TSDB: the key does not exist
PROD ERR [email protected].0.1 240426-02:02:24 red.py TSDB: the key does not exist
PROD ERR [email protected].0.1 240426-02:02:24 red.py TSDB: the key does not exist
Received syslog message from 172.16.200.10: system,info,account mikrowizard1: user admin logged out from 172.16.200.1 via api
PROD ERR [email protected].0.1 240426-02:02:24 red.py TSDB: the key does not exist
PROD ERR [email protected].0.1 240426-02:02:24 red.py TSDB: the key does not exist
PROD ERR [email protected].0.1 240426-02:02:24 red.py TSDB: the key does not exist
PROD ERR [email protected].0.1 240426-02:02:24 red.py TSDB: the key does not exist
PROD ERR [email protected].0.1 240426-02:02:24 red.py TSDB: the key does not exist
PROD ERR [email protected].0.1 240426-02:02:24 red.py TSDB: the key does not exist
PROD ERR [email protected].0.1 240426-02:02:24 red.py TSDB: the key does not exist
PROD ERR [email protected].0.1 240426-02:02:24 red.py TSDB: the key does not exist
PROD ERR [email protected].0.1 240426-02:02:24 red.py TSDB: the key does not exist
PROD ERR [email protected].0.1 240426-02:02:24 red.py TSDB: the key does not exist
PROD ERR [email protected].0.1 240426-02:02:24 red.py TSDB: the key does not exist
PROD ERR [email protected].0.1 240426-02:02:24 red.py TSDB: the key does not exist
PROD ERR [email protected].0.1 240426-02:02:24 red.py TSDB: the key does not exist
PROD ERR [email protected].0.1 240426-02:02:24 red.py TSDB: the key does not exist
PROD ERR [email protected].0.1 240426-02:02:24 red.py TSDB: the key does not exist
PROD ERR [email protected].0.1 240426-02:02:24 red.py TSDB: the key does not exist
PROD ERR [email protected].0.1 240426-02:02:24 red.py TSDB: the key does not exist
[/code]

[Matt Westfall]

Gemini says this, but I don’t want to hacky up code and it get replaced on update:

[code]
1. How to Fix the “Write” Error in red.py
When writing time-series data using RedisTimeSeries (usually via the TS.ADD or TS.INCRBY commands), Redis will often auto-create the key if it doesn’t exist. However, it will throw the TSDB: the key does not exist error if:

You are trying to apply a rule (TS.CREATERULE) to a key that isn’t created yet.

You are trying to alter a key (TS.ALTER) before it has data.

You are using a specific client wrapper or parameters that disable auto-creation.

The Fix: Wrap your write operation in a try/except block. If it fails because the key is missing, explicitly create the key (TS.CREATE) and then retry the write.

Python
import redis
from redis.exceptions import ResponseError

# Assuming ‘r’ is your Redis connection
key_name = “my_metric_name”
timestamp = “*” # * means current time in RedisTimeSeries
value = 42

try:
# Attempt to write the data
r.ts().add(key_name, timestamp, value)
except ResponseError as e:
if “TSDB: the key does not exist” in str(e):
# 1. Create the key explicitly (you can add retention, labels, etc. here)
r.ts().create(key_name)
# 2. Retry the write
r.ts().add(key_name, timestamp, value)
else:
# If it’s a different error, raise it
raise e

[/code]

[Author]

Posts