Status?

[frank gleason]

That does open the question, does anyone have a copy of the original  
mmonit?
fg


On May 2, 2007, at 9:09 AM, Michael Townley wrote:

> I have considered nagios, but the main purpose for wanting to use  
> monit over nagios is monit has far superior process monitoring and  
> it's ability to recognize depandancies and react to issues is  
> great. I can see the two working together being pretty useful but  
> difficult to set up when you want to monitor 150 machines.  The  
> long and short of it is that monit needs a centralized view.
>
> At least for my own purposes, if I have 150 client servers that all  
> have monit on them, all I need is a list of the hosts in either red  
> or green. The host names can be links to the actual monit instance  
> on that machine. If it's red, click the link and get more detail. I  
> think most of us could start making use of mmonit if it just  
> supplied a go/no-go interface for other monit instances. why is  
> this taking so long?
>
> sorry to keep whining here but, give the community CVS access to  
> mmonit's existing code base or release some api docs and feature  
> set ideas and lets get on this.
>
> Mike
>
> On 5/2/07, frank gleason <frankg at fgleason.com> wrote:
>
> Actually I have nagios and I'm trying to get rid of it. monit is  
> very good. It does need a few features, the most obvious is a  
> centralized view.
>
> fg
>
>
> On May 2, 2007, at 2:10 AM, Alexis Yushin wrote:
>
>> Hi,
>>
>> For what its worth – I do not think monit is not really suitable  
>> as a monitoring/alerting tool as  such. It is a rather process  
>> control tool which should be used in conjunction with a proper  
>> alerting system such as nagios for example.
>>
>> One can easily add tests in nagios that would be monitoring monit  
>> logfiles and raising alerts when something goes wrong.
>>
>> That's how we've solved this and it works fine!
>>
>> Alexis
>>
>>
>> On 5/1/07 9:11 PM, "Michael Townley" < mike at onshored.com> wrote:
>>
>>> I had a simple idea to write a script to connect to each monit  
>>> instance and just grep fro the hex value of red and then alert  
>>> you to the url of the instance with a red value. Once in to the  
>>> individual instance of monit, you can do whatever is needed. of  
>>> course the script could easily be ran and monitored by monit.  
>>> could even be a monit script. connect, parse the page for hex  
>>> value for red, if red, alert, if not, move on.
>>>
>>> I haven't moved forward on this due to other things on my plate  
>>> that take priority and also due to a thin hope that mmonit will  
>>> actually be out soon.
>>>
>>> I have no idea what feature set to expect from mmonit or even  
>>> what was planned for it. so as far as I am concerned, anything to  
>>> aggregate the status of multiple sites running in one place works  
>>> for me.
>>>
>>> Can we get some status from the developers besides "It will be  
>>> ready soon"? There is no reason for vaporware as long as we a  
>>> have a group of eager users and a feature set. Set up anonymous  
>>> cvs and svn or something and let us grab what you have, however  
>>> limited, and let the community go with it. I fear that inaction  
>>> from a few could really kill what has potential to be a great  
>>> project.
>>>
>>> Mike
>>>
>>> On 5/1/07, Piotrek <pki at wp.pl> wrote:
>>>> My $.01 cent, mmonit would never be released.
>>>>
>>>> :-[
>>>>
>>>>
>>>> 2007/5/1, Michael Townley < mike at onshored.com  
>>>> <mailto:mike at onshored.com> >:
>>>>> If nothing else, can you just release the code to what you do  
>>>>> have? The whole point of opensource is so that a community can  
>>>>> contribute. Open your source and let those of us who are  
>>>>> willing to put in the work, do so.
>>>>>
>>>>> My $.02
>>>>>
>>>>>
>>>>> On 5/1/07, frank gleason < frankg at fgleason.com  
>>>>> <mailto:frankg at fgleason.com> > wrote:
>>>>>>
>>>>>> Since it' s May I'll ask again. How is mmonit coming along?  
>>>>>> How about
>>>>>> a little information, like feature set...
>>>>>> _______________________________________________
>>>>>> mmonit-user mailing list
>>>>>> mmonit-user at tildeslash.com
>>>>>> http://www.tildeslash.com/mailman/listinfo/mmonit-user   
>>>>>> <http://www.tildeslash.com/mailman/listinfo/mmonit-user>
>> _______________________________________________
>> mmonit-user mailing list
>> mmonit-user at tildeslash.com
>> http://www.tildeslash.com/mailman/listinfo/mmonit-user
>
>
> _______________________________________________
> mmonit-user mailing list
> mmonit-user at tildeslash.com
> http://www.tildeslash.com/mailman/listinfo/mmonit-user
>
>
>
>
> -- 
> Michael Townley
> Technical Support - Onshore Development, LLC.
> mike at onshored.com 773-477-7019 ext 140
> _______________________________________________
> mmonit-user mailing list
> mmonit-user at tildeslash.com
> http://www.tildeslash.com/mailman/listinfo/mmonit-user

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.tildeslash.com/pipermail/mmonit-user/attachments/20070502/6247863d/attachment-0001.html