Re: Pymon doc
Duncan McGreggor
Note that additional discussion on blueprints and feature planning will
happen on pymon-dev (most folks are only subscribed to pymon).
On 12 Dec 2011 - 14:39, Mahbub....@barclayscapital.com wrote:
> Hi Duncan,
> We are thinking of using the Pymon instead of Nagios for our
> application monitoring purpose. However, there is not much document to
> go by. Have you stopped working on pymon.
I had stopped... until I got your email today, that is.
> Would it be a good idea to
> replace our nagios monitors with your pymon in that case.
For now, it would not be a good idea. However:
1) several years ago, I ran it in production for about 2 to 3 years, so
2) it probably wouldn't take too much effort to get it there again, and
3) I'm doing lots of cloud work these days, and need a light monitoring
system like pymon
4) if you and your colleagues would be interested in contributing, it
might happen even faster
On a side note, I'd like to thank you :-) I've been doing lots of
OpenStack work thee days, and have needed
* a system to monitor instances on the fly
* something I can set up easily and quickly
* something that doesn't take a lot of system resources
* a distributed monitoring system that can share data between nodes
* can be spun up easily on numerous nodes on EC2 (for example)
I had not thought about pymon in years, and so this didn't even occur to
me. After your email, however, this had changed and the project is
already receiving new life :-)
Here's what I have done today:
* converted all the old svn mirrors to git
* added a repo and README on github (https://github.com/oubiwann/pymon)
* started creating development plans for features that I need (https://blueprints.launchpad.net/pymon)
* started cleaning up old code and directories
Thanks again, and let me know if you have any questions.
d