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

If a server is down metrics are not available for any server #5

Closed
rsilva4-zz opened this issue Mar 30, 2017 · 1 comment · Fixed by #9
Closed

If a server is down metrics are not available for any server #5

rsilva4-zz opened this issue Mar 30, 2017 · 1 comment · Fixed by #9
Assignees
Labels

Comments

@rsilva4-zz
Copy link
Contributor

No description provided.

@rsilva4-zz rsilva4-zz added the bug label Mar 30, 2017
@rsilva4-zz rsilva4-zz self-assigned this Mar 30, 2017
rsilva4-zz pushed a commit that referenced this issue Apr 3, 2017
@rsilva4-zz
Copy link
Contributor Author

still failing

@rsilva4-zz rsilva4-zz reopened this Apr 4, 2017
rsilva4-zz pushed a commit that referenced this issue Apr 4, 2017
closes #5, closes #8, closes #7

Lock files kept in `/tmp` dir and cleaned up on container startup. Duplicate `cron` for `barman cron` removed.
Major refactor on exporter. Maybe Prometheus scrape interval should be in ten 5-10 minute range. Will evaluate.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant