To create a performance alert definition:
This displays the Performance Alert Definitions panel:
File Options Help
-------------------------------------------------------------–--–--------------
Performance Alert Definitions Row 1 to 3 of 3
Command ===> NEW_____________________________________________ Scroll ===> PAGE
Edit Alert Template (T) or Alert Values (S). Enter NEW command to define a new
Alert Definition.
/ Name Description Changed ID
__ PROD1XCP Production System 1 Alerts 2008/05/01 16:34 AXS
__ PROD2XCP Production System 2 Alerts 2008/05/01 16:34 AXS
__ PROD3XCP Production System 3 Alerts 2008/05/01 16:34 AXS
***************************** Bottom of data ****************************
Alternatively, you can create a new Alert Definition modeled on an existing one. Enter line action C next to the definition you want to copy. In the pop-up window, enter the name of the new definition and destination repository. If a definition of the same name already exists in the destination repository, it will not be overwritten unless you select the option Replace Alert Definition if it exists.
An Alert Definition name consists of 1-8 characters. The first character must be an alphabetic character (A-Z) or a national character (@, #, or $). The remaining characters can be alphabetic, national, or numeric (0-9) characters.
The Alert Template edit panel has four views. To cycle through the views, press Right (F11).
File Edit Confirm Options Help
EDIT Performance Alert Template - PROD4XCP Row 1 of 18 More: >
Command ===> ________________________________________________ Scroll ===> CSR_
Description . Performance Alert Definition____ Page width . . 104
Field Sort ----- Alert -----
/ Name + K O Type Function Severity Report
__ TRAN____ K A _______ RESOURCE ________ ________
__ TASKCNT_ _ _______ ________ ________ ________
__ ALERT _ _ _______ SEV_____ CRITICAL PERCENT_
__ ALERT _ _ _______ SEV_____ WARNING_ PERCENT_
__ RESPONSE _ _______ AVE_____ ________ ________
__ RESPONSE _ _______ SEV_____ CRITICAL PERCENT_
__ RESPONSE _ _______ SEV_____ WARNING_ PERCENT_
__ RESPONSE _ _______ MAX_____ ________ ________
__ CPU_____ _ TIME___ AVE_____ ________ ________
__ CPU_____ _ TIME___ SEV_____ CRITICAL PERCENT_
__ CPU_____ _ TIME___ SEV_____ WARNING_ PERCENT_
__ CPU_____ _ TIME___ MAX_____ ________ ________
__ EOR_____ _ _______ ________ ________ ________
__ APPLID__ K * _______ RESOURCE ________ ________
__ ALERT___ _ _______ SEV_____ INFO____ PERCENT_
__ RESPONSE _ _______ SEV_____ INFO____ PERCENT_
__ CPU_____ _ TIME___ SEV_____ INFO____ PERCENT_
__ EOX_____ _ _______ ________ ________ ________
******************************* Bottom of data *******************************
Enter a description and specify template details:
The template details are:
Relevant to: List and Summary reports.
List report: Only the first of multiple entries for the same field+type+alert function is reported.
Summary report: Field name ALERT provides the total count or percentage of transactions for each alert severity level (Critical, Warning, or Info) for the summary key. If no alerts are specified, the ALERT field name is ignored.
Summary report: Same function as in a Summary Report Form.
Note: The page width automatically adjusts to the calculated total length of the fields above EOR (plus one space between fields). This is in contrast to the way it works in Report Forms where you can specify the page width and EOR automatically moves to fit within the specified width.
When the template specification is complete, press F3 to save changes.
The Alert Values edit panel might have too many columns to display in a single view. Scroll Right (F11) or Left (F10) to see all columns.
File Edit Options Help
------------------------------------------------------------------------------
EDIT Performance Alert Values - EMERALDS Row 1 of 8 More: >
Command ===> ________________________________________________ Scroll ===> CSR_
1 2
Critical Warning Critical 3
TRAN APPLID SUSPEND SUSPEND CPU
/ COUNT COUNT TIME 4
H*___ 5 ________ _____________ *5_______ 7 ____________
_ HRP*____ PROD____ >10__________ >5__________ >0.5________
_ HRP*_ 6 PROD____ >7___________ >3_______ 8 >0.5________
_ HRP*____ PROD____ >5___________ >2__________ >0.5________
_ HR*_____ TEST____ >15__________ >10_________ >0.5________
_ H*______ TEST____ >20__________ >15_________ >0.5________
_ H*______ TEST____ >17__________ >12_________ >0.5________
_ H*______ FINANCE_ >23__________ >15_________ >0.5________
_ ________ ________ >27__________ <10_________ <0.5________
******************************* Bottom of data ********************************
The fields and their order in the panel are determined by the Template and are altered with changes to the Template. Only fields with Function RESOURCE and SEV from the Template are displayed here. Report fields are excluded.
This panel is used to specify the resource and threshold values associated with the resource and alert fields in the Template. In addition, the panel allows for global adjustment of threshold column values for easy alteration of thresholds.
Complete the performance alert definition by specifying threshold values:
Resource field columns remain fixed while other columns are scrollable left and right. At least one resource value must be specified in each row.
If you specify a number with a mathematical operator, all threshold values in the column are adjusted by performing the specified mathematical operation. For example, *2 will double all values in the column. If the adjusted result is negative, it is set to zero.
If you specify a number without a mathematical operator, it replaces all threshold values in the column.
If you specify both a mathematical operator and a comparison operator in the adjustment value, the comparison operator is ignored.
Press Enter to do the adjustment. The adjustment field is then cleared.
Enter RESET in the adjustment field to clear all threshold values in the column.
When the definition is complete, press F3 to save changes.
The EDIT Performance Alert Values panel allows you to specify the actual resource fields values and alert fields thresholds that constitute the alert.
You can specify different thresholds for different resource values, thus allowing you to measure different resources within the same alert report run.
The resource values are AND'd. That is, a transaction's resource values must match ALL the resource values in the alert entry to be eligible for threshold checking.
The order of the resource fields is only important when the alert definition is used in place of a Form in the report. For the List report, the resource fields will be reported in the order and position they are defined in the Template. If printed in the Summary report, they will determine the summary key, hence the summarized data values. The Summary report will generate errors if the resource fields do not conform to summary key rules.
Since you can specify one, two, or three resource fields in the Template, this panel is dynamic in terms of the number of resource field columns.
The order of the alert entries is important since a transaction's field values will only be compared against the thresholds for the first alert entry that matches the transaction's resource values. Once the resource values combination is matched, no other alert entries are checked, regardless of whether the matched entry generates an alert or not. Only when the resource values do not match, then the next entry in the alert definition is checked against the transaction. This makes it extremely important to define the resource values in the correct order when using wild characters in the resource values.
If a row contains all * (asterisk) resource values, it should be placed last in the list as it will be a catchall for transactions that don't match previous resource values. If it is placed before rows with resource values, it will render the subsequent rows irrelevant as it will match all transactions.
The threshold levels within a single field are hierarchical. That is, Critical severity is checked before Warning, which is checked before Information, with only the first exceeded threshold level reported.
Each alert field is independent of all other fields, with each field checked and reported separately.
The order of the alert fields is only important when the alert definition is used in place of a Form in the report.