[Systems] Nagios container for SL
sam at sam.today
Fri Aug 14 07:45:45 EDT 2015
On Fri, Aug 14, 2015 at 7:19 AM Samuel Cantero <scg at sugarlabs.org> wrote:
> ---------- Forwarded message ----------
> From: Samuel Cantero <scg at sugarlabs.org>
> Date: Sun, Aug 9, 2015 at 11:20 PM
> Subject: Nagios container for SL
> To: sysadmin at sugarlabs.org
> Hi all,
> I've set up a nagios container on freedom . The user is nagiosadmin and
> the password is nagios. I will change the password if you decide to keep
> this service up. Please take a look.
It looks amazing. Plus the notifications are useful.
We need to look at better auth methods though. Using 1 username and
password is probably not the most secure method. Maybe we could look into
a better password? or client certs?
We could also do the auth at the nginx level on freedom. If we wrap the
current cgi scripts in fast cgi so they can talk to nginx rather than
having apache proxied through nginx. But that is not a biggie if we can
work the auth within apache.
> I have created three hostgroups: physical servers, docker containers and
> virtual machines. Advices are welcome.
I think that for the dockers that we need to check their cpu/memory usage.
That can be done by writing a plugin . See
> I need information about what services we want to monitor on each vm
> inside justice and freedom. The main idea is not to replace munin. We just
> want to alert to the sysadmin team when a service goes down. Therefore
> sysadmin at sugarlabs.org will receive the nagios notifications unless you
> decide to change it to another email address.
> As you might guess, this won't work in case freedom goes down. If you like
> I can monitor if freedom is available through the nagios installed at my
> office and send an email to sysadmin at sugarlabs.org when freedom goes down.
You changed the freedom nagios to systems at lists because that got better
delivery, did you change your local one too?
Great idea setting up a monitor for all the machines though! It was really
weird that we got no notification when freedom went down last time, so
hopefully this will stop that from happening again.
> I couldn't create a nagios subdomain for SL because I have no access to
> ns1.slo. Anyway I have added the nagios configuration for nginx.
Sorry. My raspberry pi has given up on me, so I can't access a (way
outdated) version of dnssec-signzone that will work with the nameservers.
Anybody else able add nagios CNAME freedom?
>  http://18.104.22.168:8081/nagios3/
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Systems