Skip to content
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

How to debug scrape failures? #4

Open
stiller-leser opened this issue Jul 12, 2017 · 0 comments
Open

How to debug scrape failures? #4

stiller-leser opened this issue Jul 12, 2017 · 0 comments

Comments

@stiller-leser
Copy link

stiller-leser commented Jul 12, 2017

Hi,

first off: Thanks for writing this. I am having troubles getting this to run though. The only thing that increases for me are the 'resque_exporter_scrape_failures_total' - but how can I debug why the exporter is failing?

Here is my configuration:

resque_namespace: 'resque:admin_server'
guard_interval_millis: 0
redis:
    host: 10.1.1.1
    port: 6379
    db: 0
    password: notimportant

What do I do if I do not have any password? If I connect with redis-cli -h 10.1.1.1 -a I really could put anything into the space behind the -a.

Thanks ahead for your support!

EDIT:
Ok so I just taught myself go and how to setup your project... Turns out that the password does matter. So I guess I would need to prepare a pull request that tests wether or not a password is defined and based on the results opens the redis connection.

EDIT2:
So it turns out if password is set to an empty string '', it works fine. It even works with an empty space, but not with any arbitrary phrase like the redis-cli. A log.Fatal(err) above line 103 in exporter.go would help a lot though. This way the resque_exporter would show errors, which would be really helpful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant