; Nova Software, Inc. www.nova-sw.com ; Network Equipment Performance Monitoring System (NEPM) www.nepm.net ; Archiving and Report Builder (ARB) Control and Messages File Rev. 2.0 (031226) ; GENERAL FORMATTING RULES FOR THIS FILE: ; -This is a line-oriented control file. Each entry must appear on a single line, however long. ; Use word wrap in your editor to view lines exceeding one screen width and be certain that ; it does not silently insert extraneous newlines. ; -Optional: Comments follow the first semicolon on a line. Do not preceed the ';' with an extra space. ; Semicolons in text entries can be protected with preceeding '\'. The '\;' pair will not ; be interpreted as the beginning of a comment line. ; -Semicolon and comment may be omitted on any non-empty line. ; -The length and number of comments is unlimited. (Line length may be limited by some editors.) ; -Do not pad entries with leading or trailing spaces. ; -This file is in three sections, created by two separator lines which must begin with '::::'. ; No other line may begin with '::::'. ; -The characters ; : / \ | < > " must not appear within filenames. ; -All mail addresses must contain one and only one '@' symbol. ; *************************** SECTION 0NE: GENERAL PARAMETERS **************************** ; NOTE: THE SEQUENCE OF ENTRIES IN THIS SECTION IS FIXED--THEY MUST APPEAR IN THE ORDER GIVEN HERE! ; ENTER A '0' PLACEHOLDER FOR UNEEDED ENTRIES UNLESS NOTED OTHERWISE, TO PRESERVE ORDER. ; YOU MUST MAKE AN ENTRY IN THOSE LABELED 'REQUIRED'. ; On the following line replace the first 22 characters with your evaluation period or purchased license key. 0123456789012345678901; = License key ; Mail parameters The first four are required. Enter zero for the fifth and the sixth if not used. ; REQUIRED ENTRY: POP3 (receive) Mail server fully qualified domain name or IP address. pop3.yourdomain.com; ; REQUIRED ENTRY: SMTP (send) Mail server fully qualified domain name or IP address. ; This may be the same as your POP3 server. Reenter it in that case. smtp.yourdomain.com; ; REQUIRED ENTRY: Mail account username (for receiving files mailed from Couriers's, and for mailing alerts) NEPM-ARB; ; REQUIRED ENTRY: POP3 Mail account password for receiving mail xxxxxx; ; Comma-separated list of email addresses to receive a notice when any threshold is exceeded. ; '0' if none, meaning that alerts will only be posted to the web page, but not mailed. ; No default. receipient1@anydomain.com,recipient2@someotherdomain.com; ; TRUNCATABLE PARAMETER LIST ; The remaining parameters in this section all have default values in the Builder program. ; Unneeded items in this section following the last one to be specified may be omitted. Thus to change ; only the uptime threshold enter that line, all lines preceeding it, and omit all lines ; following it to the "::::" mark. The Builder's defaults will be used for the omitted values. ; Directory on the local file system in which to search for log files from Courier(s). ; Default is 'data/Courier' data/Courier; ; THRESHOLDS ; The following entries set the thresholds that trigger email notification of alerts ; to be sent. Positive numbers will generate an alert when the parameter exceeds that limit, ; negative numbers when it falls below the threshold. The order of these lines is fixed. ; A zero value disables the threshold check for that item. A threshold value applies to all ; monitored items of that type. A positive or negative fixed point number is required, ; including a optional decimal part following a '.', but without any comma separators ; for thousands etc. Range is unlimited. ; Invalid entries default to zero (no threshold). ; Threshold between -100 and +100 for percent uptime. ; Default is -99.0 -98.5; ; Threshold for server Access per hour. ; Default is 1000 acesses per hour -1000; ; Threshold for server BytesServed per hour. ; Default is 1000000 bytes served per hour 1000000; ; Threshold for server Errors per hour. ; Default is 10 errors per hour 10; ; Threshold for events per hour. Applies to ALL monitored events. ; Default is 1 event per hour. 1; ; MISCELLANEOUS SETTINGS ; Numbers in the following entries may include a decimal part but no comma separators. ; Size limit for the mail and data archives on disk, in Megabytes, between 1 and 4200. ; Oldest archive files are deleted when this value is exceeded until the archive size falls below this value. ; See the User Guide for more details. ; '0' is unlimited size. ; Default is 100 Mbytes. 100; ; Data age limit ; The data older than this value is not entered in the master data file and does not display in the reports. ;'0' is unlimited time (not recommended.) ; Default is 100 days. 100; ; Directory path into which to put the HTML reports. ; This is usually a secure section of a web directory tree which has been mounted on or mapped to the local filesystem. ; USE ONLY '/' AS THE DIRECTORY SEPARATOR, REGARDLESS OF OS TYPE. ; Default is 'data/web' /somewebdir/NEPM_reports; ; THE FOLLOWING SEPARATOR LINE BEGINNING WITH :::: IS REQUIRED IN THIS LOCATION IN ALL CONTROL FILES. ::::; ************** End universal parameters, begin custom parameters DO NOT REMOVE OR MOVE THIS LINE. ; *************************** SECTION TWO: CUSTOM PARAMETERS ************************************* ; (Regional and Global editions only) ; THE FOLLOWING SEPARATOR LINE BEGINNING WITH :::: IS REQUIRED IN THIS LOCATION IN ALL CONTROL FILES. ::::; ************************** End custom parameters, begin messages DO NOT REMOVE OR MOVE THIS LINE. ; **************************** SECTION THREE: EVENT MESSAGES ****************************************** ; The event messages listed in this section of the file are used to capture downtime (paired) events ; and single events of interest for the systems and elements specified. ; SPECIAL FORMATTING RULES FOR THIS 'EVENT MESSAGES' SECTION ONLY: ; -A line beginning with ~~~---~~~ must terminate each message group for each hardware or software element. ; No other line may begin with ~~~---~~~ . ; -The first non-empty line following a terminator line defines the system and element to which its following messages apply. ; Separate the system name and element name with a space. Neither name may contain a space. ; -Leave no empty or blank lines within each element's group of message text lines. Empty lines may only appear after a terminator line. ; -The system type and element names used here must match the spelling used in the sending Courier's control file ; for the same item. Case is irrelevant in both control files and is ignored. ; -Element names may contain only alphanumeric characters and '_', without spaces. ; -Message groups may appear in any order. ; -Messages may appear within a group in any order. ; -Use the shortest message text required to make it unique, for best Builder performance. ; -Exclude variable information such as dates and times, IP addresses, etc. from your message entries. ; -The rules for inserting comments are the same as given in the GENERAL FORMATTING RULES at the beginning. ; -PERFORMANCE MONITORING SYNTAX: ; -For each element one base filename in NCSA (common) log format may be specified for performance monitoring. ; -Any combination of Accesses, KBytesTransferred or MBytesTransferred, and Errors per unit time can be monitored on such logs. ; -Append to the element name separated by a space the performance item names in angle brackets thus: ; ; -Append to the last performance item (no space) the base name of the element's log file to monitor for these performance items. ; -Performance item names may include only alphanumeric characters and the underscore, '_'. ; -Performance item names are case insensitive. ; -Each performance item name must include one (and only one) of the words 'Accesses', 'KBytesTransferred', 'MBytesTransferred', ; or 'Errors' to create a corresponding performance report for its element name (case insensitive.) ; -Performance reports default to a 1 hour time increment if no other time bin is specified. ; -A time bin (graph increment) may be specified by appending '_iDjHkMlS' to the performance item name in which ; i = an integer number of days between 1 and 27, ; j = an integer number of hours between 1 and 23, ; k = an integer number of minutes between 1 and 59, and ; l = an integer number of seconds between 1 and 59 for the increment ; Enter only the number(s) and descriptive character(s) (d,D = days, h,H = hours, etc.) needed, in any order, ; such as '_1D' for one day, or '_30min2hr' for 2.5 hours. D,H,M, and S may be upper or lower case. ; The total time bin increment is the total time defined by i,j,k,and l. ; ; -Sample: Unix Apacheaccess_log plots Accesses every hour, MBytes every 4 hours, ; and Errors every 3 days, 4 minutes and 3 seconds ; for the access_log of the element 'Unix Apache'. ; Unix System ;syslogd startup succeeded; preceeds kernel log daemon startup klogd startup succeeded; beginning of true controlled startup klogd shutdown succeeded; last logged event in controlled shutdown ;ACCESS DENIED ;FTP LOGIN REFUSED ;session opened for user ~~~---~~~ Unix Apache access_log; httpd httpd startup succeeded httpd shutdown succeeded ~~~---~~~ Unix inetd inetd startup succeeded inetd shutdown succeeded ~~~---~~~ WinNT System The Event log service was started. The Event log service was stopped. ;The previous system shutdown at ~~~---~~~ WinNT IIS ~~~---~~~ WinNT NIC ~~~---~~~ WinNT Apache ~~~---~~~ IOS System ~~~---~~~