[CUWiN-Dev] Existing CUWiN monitoring tools and proposed work for monitoring tools

[Chase Phillips]

Can you provide more context?  Are you scoping requirements for a
CUWiN monitoring system?

On 8/8/06, dan blah <dan.blah at gmail.com> wrote:
> i have to have this *formalized* by tomorrow.  any additions,
> subtractions, edits let me know.
>
> existing tools...
> none <insert tool here>
>
> proposed work...
> monitoring of network service status (inetd, zebra, hslsd, dhcpselect,
> wdogctl, etc)
> monitoring of node recourses (processor load, disk and memory usage,
> running processes, network load)
> monitoring of environmental factors such as node temperature
> monitoring of system state changes (network interface changes,
> configuration file add/delete/changes, file/drive permission changes)
> list of node clients with basic client information
> web interface for viewing current network status, problem history, log
> file (/var/log/daemon, /var/log/messages), application and kernel
> routes
> web interface visible nodes (parsing of /var/db/linkstates, routeviz)
> web interface authorization
> ability to define event handler to be run during service of host
> events for proactive problem resolution and self healing nodes
> contact notification when service of host problems occur and get
> resolved via email
> local node engine viewable from local httpd or console with the
> ability to be queried from a remote management engine
> --
> Daniel
> _______________________________________________
> CU-Wireless-Dev mailing list
> CU-Wireless-Dev at lists.cuwireless.net
> http://lists.chambana.net/cgi-bin/listinfo/cu-wireless-dev
>