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

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

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231

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:
statport statport_1g statport_2g statport_4g
VARCHAR(32) NOT
NULL
data_table
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
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
Defines an additional condition that must be met for certain alerts
to be generated. See
“Condition” (page 121)
.
VARCHAR(32)
condition_code
Defines a value used in conjunction with condition_code. See
“Condition Value” (page 122)
.
DOUBLE PRECISION
NOT NULL
condition_val
The email address to which alerts for this rule should be sent.
VARCHAR(64)
recipient
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