Discussion:
[Monitorix-general] A centralized status board for multiple Monitorix servers
Jaime Gómez Obregón
2015-08-27 20:35:23 UTC
Permalink
Hi there.

I have the need to monitor several servers and found Monitorix’ “multi host” feature not ideal to my use case — mainly because I wanted to combine a given metric from multiple servers into a single chart, for easier monitoring, comparison and correlation; and to customize the whole dashboard to suit my particular needs.

Thus I started building a custom centralized board for multiple Monitorix servers, which I have called monitorix-board and is available under the GPL:

https://github.com/JaimeObregon/monitorix-board <https://github.com/JaimeObregon/monitorix-board>

The dashboard is HTML5 and JavaScript based, so there are no server-side dependencies, and is easily customizable from a simple JSON files, an approach which in my opinion would be great to see in Monitorix <https://github.com/mikaku/Monitorix/issues/53>, as the current hardcoded markup generated from Perl scripts is impossible to customize.

Regards,
--
Jaime GÓMEZ OBREGÓN
Director

<http://www.iteisa.com/>  <http://www.iteisa.com/>
ITEISA DESARROLLO Y SISTEMAS, S.L.
Benidorm, 8 bajo. 39005 Santander. España.
Teléfonos: 902055277, 942943483 y 691152158
www.iteisa.com <http://www.iteisa.com/> · twitter.com/iteisa <http://www.twitter.com/iteisa> · fb.com/iteisa <http://www.fb.com/iteisa>

Sólo hacemos cuatro cosas, pero las hacemos muy bien <http://www.iteisa.com/dossier.pdf> (PDF, 1,3 MB)
Jordi Sanfeliu
2015-09-01 14:10:32 UTC
Permalink
Hi Jaime,

Thanks for your effort on making such new dashboard to monitor multiple
servers.

I'm aware that the current Multihost feature in Monitorix is old and
rigid, and indeed it needs a complete rewrite. That's something that I
have in my TODO list since some time ago.

Ideally though, I think that the best way would be that all of you that
know very well the modern web techniques will be willing to help to
change the current Perl code output (pure <HTML>) to a pseudo-code
(something like a template), in order to later be 'completed' by a
front-end code or something.

I'm always more focused in the low level parts of Monitorix (daemons,
collecting system values, etc.) and it's clear that Monitorix needs the
help of someone that knows better 'the other side' of the game. :)

Maybe we can work together on the same direction.
Thanks.
Post by Jaime Gómez Obregón
Hi there.
I have the need to monitor several servers and found Monitorix’ “/multi
host/” feature not ideal to my use case — mainly because I wanted to
combine a given metric from multiple servers into a single chart, for
easier monitoring, comparison and correlation; and to customize the
whole dashboard to suit my particular needs.
Thus I started building a custom centralized board for multiple
Monitorix servers, which I have called *monitorix-board* and is
*https://github.com/JaimeObregon/monitorix-board*
The dashboard is HTML5 and JavaScript based, so there are no server-side
dependencies, and is easily customizable from a simple JSON files, an
approach which in my opinion would be great to see in Monitorix
<https://github.com/mikaku/Monitorix/issues/53>, as the current
hardcoded markup generated from Perl scripts is impossible to customize.
Regards,
--
*Jaime GÓMEZ OBREGÓN*
Director
--
Jordi Sanfeliu
FIBRANET Network Services Provider
http://www.fibranet.cat

------------------------------------------------------------------------------
Loading...