check_logfiles is a plugin for Nagios which checks logfiles for defined patterns. It is capable of detecting logfile rotation. If you tell it how the rotated archives look, it will also examine these files. Unlike check_logfiles, traditional logfile plugins were not aware of the gap which could occur, so under some circumstances they ignored what had happened between their checks. A configuration file is used to specify where to search, what to search, and what to do if a matching line is found.
check_hpasm is a plugin for Nagios which checks the hardware health of Hewlett-Packard Proliant servers. To accomplish this, you must have installed the hpasm package. The plugin checks the health of processors, power supplies, memory modules, fans, CPU- and board-temperatures, and alerts you if one of these components is faulty or operates outside its normal parameters.
check_aaccli is a plugin for Nagios which checks the hardware health of Adaptec SCSI RAID controllers. To accomplish this, you must have installed the aaccli binary (from the aacapps package). The plugin checks the error log of single disks (with S.M.A.R.T.) and the health of mirror containers.
check_sstcam is a plugin for the Nagios monitoring system that checks the alarm directory of a SUN Storagetek Common Array Manager.The CAM is management software for the Sun StorEdge 6130 and Sun StorageTek 6140 and 6540 Storage arrays. Warnings and failures of the managed systems will be written as files into the alarm directory. The check_sstcam plugin reads this directory periodically and forwards newly reported alerts to Nagios.
check_oracle_health is a plugin for the Shinken (Nagios) monitoring software that allows you to monitor various metrics of an Oracle database. It includes connection time, SGA data buffer hit ratio, SGA library cache hit ratio, SGA dictionary cache hit ratio, SGA shared pool free, PGA in memory sort ratio, tablespace usage, tablespace fragmentation, tablespace I/O balance, invalid objects, and many more.
check_mysql_health is a plugin for the Shinken (Nagios) software that allows you to monitor a MySQL database. Among the list of metrics are time to login, index usage, bufferpool hit rate, query cache hit rate, slow queries, temp tables on disk, table cache hit rate, connected threads, and many more. Requirements are either a DBD::mysql Perl module or a MySQL client package.
check_mssql_health is a plugin for Nagios that allows you to monitor an MS SQL Server. Among the list of metrics are time to login, buffer cache hit rate, page life expectancy, full table scan rate, free space in databases, batch requests/second, and many more. Installation of the DBD::Sybase Perl module is required.
check_db2_health is a plugin for Nagios that allows you to monitor DB2 database servers. Itcan operate in several modes: measuring how long it takes to connect and log in; display the number of connected users; display percentage of synchronous reads (SRP); display the percentage of asynchronous writes; display hit ratio in Buffer Pools, or only in Data Pages or Index Pages; display the percentage of SELECT that use an index; display the number of deadlocks per second; display the number of lock requests per second that could not be satisfied; display the fraction of time which was spent waiting for locks; display used space in a database or tablespace; display free space in a tablespace (in contrast to the previous mode, you can use units (MB, GB) for the thresholds); or display used space in a database log.
check_nwc_health is a plugin for the Shinken (or Nagios/Icinga) monitoring system. It is used to check hardware health, environment, interfaces, pools, uptime, etc. of a great range of the most popular network components like switches, routers, firewalls, proxies, load balancers, etc. Currently it can monitor: Cisco IOS, Cisco Nexus, F5 BIG-IP, CheckPoint Firewall1, Juniper NetScreen, HP Procurve, Nortel, Brocade 4100/4900, EMC DS 4700, EMC DS 24, Allied Telesyn, and Blue Coat SG600.
Re: why not script(1)
> Hi there,
> what are the benefits of using rootsh
> instead of script(1)?
- doesn't send the in/output to a syslog server
- cannot be used as a login shell
- does not detect logfile tampering
- cannot be restricted to particular commands