SV: Simple windows client

[Bergström Sebastian]

Right on the spot! I've been thinking about this as well.

There must be many people monitoring Windows hosts?
Sad but true, that is all that I monitor right now, and it's all done with simple NSClient stuff so there is nothing special about that.

It seems to me that the most competent Windows monitor agent today is NRPE_NT but I can't say for sure cause I haven't looked into it as deep as I need to. NRPE_NT needs some heavy scripts and configuration to do wonders as I understand.

Any good scripts or ideas are welcome.

One way to accomplish what you're asking for is to collect all stuff different people are using and then select the most useful stuff and finally get the stuff together in one neat Windows monitor package. This can easily be done with something as simple as a batch file.

I can volonteer for the latter if you who reads this can send me your scripts and configuration. Just specify what does what and I believe I can figure out the rest.

I will follow this thread with great interest.


Best regards,
Sebastian Bergstroem
SWEDEN

-----Ursprungligt meddelande-----
Från: Johan Barelds [mailto:mailings at good-it.com] 
Skickat: den 15 september 2005 20:45
Till: Nagios-users at lists.sourceforge.net
Ämne: [Nagios-users] Simple windows client

Hi all,

I am using Nagios for a while now and i am a true believer.
We do have around 200 window servers in our environment which need to be monitored and Nagios does the job quit well.
Unfortunaly it's rather labour and study intensive to get a complete set of windows clients/scripts that fullfills ones monitor needs;

Until now i haven't found a windows client which was:

a. an out-of-the-box installation (e.g. msi file) and b. having a very simple gui in which all the configuration stuff could be done in a very intuitive matter and c. has all the needed monitor functionality in this one client (like eventlogs, perfmon counters, disk/cpu/mem usage etc.) and d. produced a single conf file which could be distributed quit easy to simular windows servers to prevent manual configuration on each server and e. has a large installed base so feedback and corrective actions on bugs/feature requests is quit good.

Is it an idea to develop such a "general windows client" instead of making a lot of smaller programms, scripts by a lot of people, which needs a lot of studying/implementing/configuring etc. to get it working?

Unfortunatly i am not a programmer otherwise i would have made it myself..:-) But it would be nice if there are some programmers around who are interested in starting such a project.
I am very curious if i am the only one looking at it this way or if there is "a market" for such a new windows client.

Please let me know your thoughts...

--
Kind Regards / Met vriendelijke groet,
Johan Barelds


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. 
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null




-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. 
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null