[arch-devops] Changing the monitoring for new servers

Sven-Hendrik Haase svenstaro at gmail.com
Thu May 12 06:17:05 UTC 2016

Alright, thanks for the feedback guys. We'll roll with zabbix + grafana.

barthalion, I like your suggestion about making the AUR maintainer a TU.
Will you handle that?

I'll set up our new servers in the mean time.

On May 11, 2016 9:02 AM, "Bartłomiej Piotrowski" <bpiotrowski at archlinux.org>

> On 2016-05-05 15:57, Sven-Hendrik Haase wrote:
> > Would be interested in hearing your thoughts. If you have something to
> > add, just add numbered bullet points. If nothing comes of this, we'll
> > probably go back to munin.
> >
> > Sven
> I completely fail to see any advantages of 2 and 5. Prometheus isn't
> much older that what I proposed with InfluxDB stack (and I didn't
> mention Ansible usage there for alerting).
> I'd really like to give Sensu a shot, but I already said some snarky
> comments about complicated projects with the need of MQ, so let's skip it.
> Given that there is Grafana plugin for Zabbix, I guess it's the best
> option considering our low number of machines to monitor. It covers both
> graphing and alerting, so sounds very good to me. We should also
> consider promoting its AUR maintainer as I remember he packages it for
> quite a long time and PKGBUILD is quite flawless.
> Bartłomiej
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.archlinux.org/pipermail/arch-devops/attachments/20160512/7f3ef97b/attachment.html>

More information about the arch-devops mailing list