Direction, Limit value, Limit count – HP 3PAR System Reporter Software User Manual

Page 121: Condition, Condition value, Recipient, Example of an alert rule

Advertising
background image

Table 57 Metric (continued)

Data Tables

Description

Metrics

statcpu

Percentage idle time for the node

idle_perc

statport, statpd,

nl

Total utilization per second. For instance,
when the PD utilization exceeds a given

total_utilperc

statpd_nl7,statpd_fc10,

nl

high (say 90%) utilization meaning that

statpd_fc15, statpd_ssd150, statld,

nl

90% of the time there is some IO
operation outstanding at the PD.

statvlun

Direction

Specifies whether the Metric should be less than (<) or greater than (>) the Limit Value for the alert
to be generated.

Limit Value

Specifies the value that the Metric is compared to. This should be a number.

Limit Count

The alert will only be generated if the number of objects for which the Metric exceeds the Limit
Value (in the direction specified by Direction) is greater than Limit Count in any given sample. This
should be an integer.

Condition

Specifies the condition (min_read_iops, min_write_iops, min_total_iops) that should be monitored.

Condition Value

Specifies the condition value.

Recipient

Email address to which the alert email should be sent.

Example of an Alert Rule

Figure 47 (page 121)

shows an example of a configured alert. In this example, System Reporter

will send an email alert to email@address each time it inserts a high-resolution sample in which
more than 0 (Limit Count) VLUNs (including VLUNs in all systems) has a total (reads and writes
included) average service time in millisecs of greater than (>) 1000 (Limit Value).

Figure 47 Example of an alert rule

An example of the email alert is shown

Figure 48 (page 122)

:

Configuring Rules for Email Alerts

121

Advertising
This manual is related to the following products: