Re: Cricket monitoring

Hi George,

It is active now and then when someone has a question how to achieve a 
certain configuration. After looking at the configuration examples and 
the manual cricket is pretty straightforward. It helps if you know about 
perl, understand SNMP and read up on RRD.

There are some well known problems with 64bit systems, never versions of 
RRD and some bugs in the code about the monitoring thresholds.

The real beauty about cricket being open source is that you just have to 
have a look the the perl code itself and that will answer most of your 
questions.

I have used it at two companies now. Monitoring up to 200 boxes. SUNs, 
HP, Linux boxes, Cisco gear, Fortinet boxes, OpenVMS systems,  ... On 
the service side anything from SMS throughput, web servers, E1 
interfaces, CPU load, .... the possibilities are endless.

You can really monitor whatever you want, either with snmp or any kind 
of executable/script that provides counters for a services. There are 
also some tools that will help to generate configuration of a lot of 
network equipment.

Currently i do use a combination of Nagios and Cricket. Nagios does the 
alarming and cricket the performance monitoring of the services.

Br,
  Oliver

Monappallil, George wrote:
> Guys:
> How active is this forum ? I'd like to know how well supported Cricket
> is by the opensource community before committing to it at my company. 
>
> Thanks,
>
> - George
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> cricket-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/cricket-users
>   


------------------------------------------------------------------------------