-
Notifications
You must be signed in to change notification settings - Fork 886
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Redis_exporter do not rebase after redis restarts #257
Comments
Nothing else in the logs? Can you try running the exporter with the You could also try updating to a more recent version of the exporter, 0.34.0 is the last one. |
debug log:
|
|
have no idea, i have found some issues according to "first path segment in URL cannot contain colon" also i have change public ip to 127.0.0.1 in "-redis.addr=" fllag
debug logs starts:
|
Could you try |
or u mean -redis.addr="redis://127.0.0.1:6379" ??? |
Yes, |
|
I have found, that after each redis restarts, requirepass in /var/vcap/store/redis/redis.conf is chenging each time |
Ok, weird. So we can close this? |
can redis_exporter reread redis.file if it changed? Maybe we can propose some reload config functional for this ? |
I see what the problem is. I think password file refresh would be a possibility but with the advent of PR #256 this logic will all be removed from the exporter and should be pushed up into your SD / Prometheus server. |
yea it's refresh the password from the file |
@oliver006 so in v1.0.0 it's possible to refresh password file ? |
Unfortunately, no. You'll have to move that reload functionality into your orchestration system and pick up the new password there and propagate it to the exporter. |
Not an exporter issue, closing this. |
After redis restarts: we got RedisExporterScrapeError:
max by(instance) (redis_exporter_last_scrape_error) != 0
bulk of redis instances with the same problem:
It's going to normal after redis_exporter restart:
redis_exporters logs :
Do we have any solution except redis_exporter restarts ???
The text was updated successfully, but these errors were encountered: