HP 3PAR StoreServ 7200 2-node HP 3PAR System Reporter 3.1.0 Software User& - Page 194
The alertconfig Table, The scheduled_report Table, Table 61 system_4 Table
View all HP 3PAR StoreServ 7200 2-node manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 194 highlights
Table 61 system_4 Table (continued) Column Type system_model VARCHAR(32) NOT NULL CHSIZEMB INTEGER NOT NULL Comment System hardware model, for example: InServ S400X InServ T400 Indicates the chunklet size. The alertconfig Table The alertconfig_2 table contains a row for each alert configuration rule. Table 62 alertconfig_2 Table Column alertid data_table resolution inserv metric direction limit_val limit_count condition_code condition_val recipient Type Comment INTEGER PRIMARY KEY A unique identifier for each rule. (AUTO_INCREMENT) VARCHAR(32) NOT NULL The data table on which the rule operates. Currently supported values are: statport statport_1g statport_2g statport_4g statport_8g statport_hostnodesum statport_nodesum statport_disknodesum statport_syssum statpd, statpd_nl7 stapd_fc10 statpd_fc15 statpd_ssd150statpd_sum statpd_nl7sum statpd_fc10sum statpd_fc15sum statpd_ssd150sum statld statvlun statcpu VARCHAR(32) NOT NULL The sample resolution, one of hires, hourly or daily. VARCHAR(32) NOT NULL The system name that the alert rule is applied to. If this is the empty string (blank) then the alert rule is applied to all systems. If this is not the empty string, it should match one of the values in the name column of the system_3 table. VARCHAR(32) NOT NULL The metric that is calculated. The supported values depend on the data_table value. VARCHAR(32) NOT NULL How the metric is compared against the limit_val. Currently this should be either > (greater than) or < (less than). DOUBLE PRECISION NOT NULL The calculated metric is compared based on direction against limit_val. INTEGER NOT NULL In each sample interval if the number of objects for which the metric values exceed limit_val when compared using direction is greater than limit_count then an email alert is generated. VARCHAR(32) Defines an additional condition that must be met for certain alerts to be generated. See "Condition" (page 121). DOUBLE PRECISION NOT NULL Defines a value used in conjunction with condition_code. See "Condition Value" (page 122). VARCHAR(64) The email address to which alerts for this rule should be sent. The scheduled_report Table The scheduled_report_2 table contains a row for each scheduled report and defines where the report should be stored, when it should be run and parameters used to generate the report. 194 Database Schema