1. August 28, 1998New features in PATROL 3.01 New features in PATROL version 3 Michael Jung (TU-Berlin), Waltraut Niepraschk (DESY) System overview Patrol actions and resources control Configuration WWW Interface Patrol usage

2. August 28, 1998New features in PATROL 3.02 Patrol 3.0 n based on SLAC patrol by C. Boheim n modified and extended by M. Jung n WWW interface in Javascript available supported architectures AIXIRIX SunOSLinux SolarisDEC-Unix HP-UX easy adaptation to new architectures by specifying patterns for the output of certain system commands

3. August 28, 1998New features in PATROL 3.03 Patrol resources control Obtaining information on processes and daemons (ps) file systems (df) file sizes (ls) services and ports (netstat) hosts (uptime) return codes or timing (timeout) of arbitrary commands Resource checks are based on value and change of value (as compared to last run of patrol) Tests on limits (value, value+delta, (val1, val2, val3+delta) with relops (>, <, =, !=, =~/regexp/)

4. August 28, 1998New features in PATROL 3.04 Patrol actions If tests fulfil specified criteria, perform actions: mail (to users, to admins) kill (processes) nice (processes) restart (daemons) write (to syslog) execute system commands execute snippets of perl code (access to patrol internal variables) Mail texts, system commands and perl snippets are defined in blocks for easier reference

5. August 28, 1998New features in PATROL 3.05 Patrol configuration n patrol actions are defined as rules in a configuration file n rules do act on targets (identified by hostname, ostype, netgroup,...) rule format: rule_type target resource condidion action rule types: Ffile systemHLhost, load limit DdaemonHThost, uptime limit SPsystem portHUhost, user limit PCprocess, cpu limitCCcommand, exit code PMprocess, memory limitCTcommand, time out PTprocess, time limitWfile size PNprocess, number limitSPservice port

6. August 28, 1998New features in PATROL 3.06 Configuration examples n restart sshd and notify admins by email D*sshdrestart(“sshd”), mail(admin, MD) n renice some jobs on IRIX systems (not Codine batch jobs) PC[irix]!{cod_}>50%nice(8), mail($user, admin, MPC) n watch the /usr1 file system on host hydra Fhydra/usr1>95%mail(admin, MF1) n notify admins, if load on aisa machines is above 2 HLaisa[0-9]>2 mail(admin, MHL) n notify admins, if /etc/check has nonzero return code (netgroup hps) CC(hps)/etc/check >0mail(admin, MCC)

7. August 28, 1998New features in PATROL 3.07 WWW Interface n patrol runs periodically (cron) on all hosts to be checked, no communication between hosts, no central information retrieval n WWW interface runs periodically on a single host (WWW server) u gathers information on all hosts over a (configurable) period of time u consists of a perl script (part of patrol) and Javascript HTML files (generated by patrol) u provides both global view of the system, information on (configurable) subgroups and on individual hosts u can also process and display data from other (monitoring) tools n see screen dump of our system in routine use

8. August 28, 1998New features in PATROL 3.08 Patrol usage at DESY Zeuthen n presently approximately 100 hosts controlled by patrol n patrol started by cron every 15 minutes Controlling tasks on all hosts n Load monitoring n Execution time monitoring of user processes (except batch) n Presence of important daemons (cron, xntp, syslog, afs, batch, …) Tasks on selected hosts (usually servers) n File system usage (/, /usr, /tmp, /home, …) n presence of daemons (named, sendmail, …) Depending on the problem appropriate actions are taken (mail, restart, log, …) Observed increased stability of services for users