The alertconfig table – HP 3PAR System Reporter Software User Manual
Page 192

Table 61 system_4 Table (continued)
Comment
Type
Column
System hardware model, for example:
VARCHAR(32) NOT
NULL
system_model
InServ S400X
InServ T400
Indicates the chunklet size.
INTEGER NOT NULL
CHSIZEMB
The alertconfig Table
The alertconfig_2 table contains a row for each alert configuration rule.
Table 62 alertconfig_2 Table
Comment
Type
Column
A unique identifier for each rule.
INTEGER PRIMARY KEY
(AUTO_INCREMENT)
alertid
The data table on which the rule operates. Currently supported
values are:
nl
VARCHAR(32) NOT
NULL
data_table
statport
nl
statport_1g
nl
statport_2g
nl
statport_4g
nl
statport_8g
nl
statport_hostnodesum
nl
statport_nodesum
nl
statport_disknodesum
nl
statport_syssum
nl
statpd, statpd_nl7
nl
stapd_fc10
nl
statpd_fc15
nl
statpd_ssd150
nl
statpd_sum
nl
statpd_nl7sum
nl
statpd_fc10sum
nl
statpd_fc15sum
nl
statpd_ssd150sum
nl
statld
nl
statvlun
nl
statcpu
The sample resolution, one of hires, hourly or daily.
VARCHAR(32) NOT
NULL
resolution
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.
VARCHAR(32) NOT
NULL
inserv
If this is not the empty string, it should match one of the values
in the name column of the system_3 table.
The metric that is calculated. The supported values depend on
the data_table value.
VARCHAR(32) NOT
NULL
metric
How the metric is compared against the limit_val. Currently this
should be either > (greater than) or < (less than).
VARCHAR(32) NOT
NULL
direction
The calculated metric is compared based on direction against
limit_val.
DOUBLE PRECISION
NOT NULL
limit_val
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.
INTEGER NOT NULL
limit_count
192 Database Schema