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

CPANTesters Monitoring #16

Open
preaction opened this issue Sep 12, 2016 · 2 comments
Open

CPANTesters Monitoring #16

preaction opened this issue Sep 12, 2016 · 2 comments
Labels

Comments

@preaction
Copy link
Member

Rather than having random people e-mail us when things are broken, we should have an automated monitor in-place. This means setting up another machine in another data center and installing/configuring a monitoring system like Nagios, Zabbix, Icinga, or Shinken.

Known issues to monitor immediately:

  • Machine is alive
  • Website is alive
  • Disks are not full
    • /media/backend has at least 50G free
  • Backup is running
    • /media/backend/cpantesters/dbx has backup files from this week
  • Reports release is running
    • MySQL tables cpanstats.release_data and cpanstats.release_summary have MAX(id) that is not too far out of sync with MAX(id) from cpanstats.cpanstats
preaction added a commit to cpan-testers/cpantesters-deploy that referenced this issue Sep 12, 2016
I've bought a new machine, monitor.preaction.me, and have configured
Icinga2 on it. In the Rexfile, I've documented what I needed to do to
install and configure Icinga2 on the OpenBSD 6.0 machine I bought.
I likely need to see how to add better OpenBSD integration into Rex so
I'm using Rex functions instead of raw commands.

The Icinga2 config file I've started will eventually contain actual
monitors for various parts of the system as I come across things that go
down.

Refs cpan-testers/cpantesters-project#16
@preaction
Copy link
Member Author

preaction commented Sep 12, 2016

I've installed Icinga2 on a new machine, monitor.preaction.me. I've started a config file for cpantesters and set up a single host-alive check. I will continue with the rest of these checks soon.

@preaction
Copy link
Member Author

Icinga2 is really difficult to manage, so we're going to try Graphite+Grafana for now to see if it works easier.

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

No branches or pull requests

1 participant