In addition, events in the log are monitored and automated alpha-numeric pages sent to the appropriate people when certain thresholds are reached.
Entries in the log are made as follows:
$ @clu$manager:log 'f$environment("procedure")' PROBLEM_TAG "Problem descrition..."
Where "PROBLEM_TAG" is a unique tag for each type of problem. There
is as of yet no set method for determining these tags. Just choose
one that doesn't yet exist. The "Problem description..." can be any
text the user wishes. Usually kept to a few words.
For instance the following line executed from the proceedure systartup_vms.com:
$ @clu$manager:log 'f$environment("procedure")' NODE_REBOOTED "Node SCSW5 Rebooted"
Would make the following entry in the log:
10:43:10 SYSTARTUP_VMS NODE_REBOOTED Node SCSW5 rebooted.
Example: DISK$SLD_FAC0:[SLDWWW.SYSLOG]NODE_REBOOTED.HTML
Create your file copying the form of one of the existing problem tag html files.
Follow the comments in the file. There are four lines that must be edited. First, add the problem tag to the line:
@problems = (...);Next, indicate here the name of the person to be paged for a given problem tag in the line:
%person_to_page = (...);(N.B. This person must have an alpha-numeric pager that is setup to be used with the TelAlert system)
Finally, enter the thresholds for paging during normal hours (8 a.m. to 10 p.m.) and critical hours in the respective lines:
%normal_threshold = (...); %critical_threshold = (...);In order for these changes to take effect, the running version of this program must be stopped and restarted. For the time being, contact Mike Wendling for this.