You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What version of redis_exporter are you running?
Please run redis_exporter --version if you're not sure what version you're running.
[x] 6.6.0
[ ] 0.3x.x
[ ] 1.x.x
Running the exporter
It's being run via your helm chart with default values. I'm currently testing this by manually editing the deployment and adding the environment variables in the running deployment.
Also getting all of these "parseKeyArg(): Got empty key arguments, parsing skipped" is mildly misleading or at least very confusing.
Expected behavior
There is no redis_keys metric. Moreover, the logs may be indicating 0 finds, while there are ~7000 keys in the current db matching the pattern I've specified. I was expecting something propagated to redis_keys (or some key metric that didn't already exist before this change).
I'll continue reading through your code to see if I notice anything.
The text was updated successfully, but these errors were encountered:
Describe the problem
We're running the exporter in k8s. I've invoked the exported using env vars for
REDIS_EXPORTER_CHECK_KEYS
with:with logging enabled, the following is seen in the logs:
What version of redis_exporter are you running?
Please run
redis_exporter --version
if you're not sure what version you're running.[x] 6.6.0
[ ] 0.3x.x
[ ] 1.x.x
Running the exporter
It's being run via your helm chart with default values. I'm currently testing this by manually editing the deployment and adding the environment variables in the running deployment.
Also getting all of these
"parseKeyArg(): Got empty key arguments, parsing skipped"
is mildly misleading or at least very confusing.Expected behavior
There is no
redis_keys
metric. Moreover, the logs may be indicating 0 finds, while there are ~7000 keys in the current db matching the pattern I've specified. I was expecting something propagated toredis_keys
(or some key metric that didn't already exist before this change).I'll continue reading through your code to see if I notice anything.
The text was updated successfully, but these errors were encountered: