Top
Systemwalker Service Quality Coordinator User's Guide
Systemwalker

10.1.1 Definition Method

This file is in CSV format. Each item that will be subject to threshold monitoring is defined on a separate line.

Column

Description

1

The threshold monitoring ID. Use a unique ID for each line.

Note

When using the agent for Agentless Monitoring function

Add "|<host name>" after "threshold monitoring ID", with "<host name>" being the name of the host to be monitored when monitoring more than one server using the agent for Agentless Monitoring function on a Manager/Proxy Manager.

<threshold monitoring ID>|<host name>

  • For the server monitored by Agent for Agent-based Monitoring function

Use the host name specified in "DISPLAYNAME" in the remote monitoring configuration file (remoteAgent.txt).

  • When doing threshold monitoring of Manager/Proxy Manager itself.

Use the host name displayed in the sqcSetPolicy.

Example:
If the threshold monitoring ID is "AlertID1" and the name of the host to be monitored is "hostnameA":
AlertID1|hostnameA

Wildcards can be used for host names.
Example:
If the host name is "aaabbbccc", then any of the following examples will match it; "aaabbbccc", "aaa*", "aa?bb?cc?" , "???bbb???", "[abc]aa[abc]bb[abc]cc".

If "|<host name> is not added, then all servers being monitored will also have their threshold monitored.

2

The record number for the item being monitored. See "The correspondence between record numbers and field names for monitored items" for record number values.

3

Field name + record number of the item being monitored.

Example: To monitor field name "usrproc" and record number "1052", specify "usrproc1052".

See "The correspondence between record numbers and field names for monitored items" for field name and record number values.

4

Define the resource ID of the resource being monitored.

The resource ID can be seen in the Resource ID column by displaying the content of the target node in the Console's Drilled-Down view.

Wildcards can also be used in the resource ID.

For example, if the resource ID is "aaabbbccc", then any of the following specifications will match this resource ID:
"aaabbbccc", "aaa*", "aa?bb?cc?", "???bbb???", or "[abc]aa[abc]bb[abc]cc", and so on.

5

Define the name that will be used to send notifications regarding the monitored item.

6

Define the starting time for the time period for which threshold monitoring will be performed. Specify the time using HH:MM:SS format. This item cannot be omitted. For continuous monitoring (24 hours a day), specify "00:00:00" as the starting time.

7

Define the finishing time for the time period for which threshold monitoring will be performed. Specify the time using HH:MM:SS format. This item cannot be omitted. For continuous monitoring (24 hours a day), specify "00:00:00" as the finishing time.

8

Define the threshold violation count (N), which is the number of times (within the standard sampling count) that the threshold has to be exceeded before an alert will be notified.

9

Define the standard sampling count (M) for determining alert notifications. The maximum standard sampling count is 9 and the minimum value is 1. Specify an integer between 1 and 9 inclusive. If the sampling count is 1, define the threshold violation count as 1 as well.

Define the threshold violation count (N) and the standard sampling count (M) so that the following relationship exists: N M/2

10

Warning threshold

11

Error threshold

12

Define either "<" or ">".

>: Sends an alert notification if the value exceeds the threshold (useful for monitoring CPU usage, etc.).

<: Sends an alert notification if the value drops below the threshold (useful for monitoring available memory, etc.).

Point

  • The values that can be specified as the warning and error thresholds in the threshold monitoring definitions are as follows:

    • Integers

    • Real numbers (up to 15 decimal places can be specified)

    • Negative values can also be specified.

  • It is not possible to specify only warning thresholds or only error thresholds in the threshold monitoring definitions.

  • If a value that cannot occur (ex. To monitor thresholds for CPU usage, specify "120%" for the error threshold) is specified for the warning threshold, alarms will not be notified even if the error threshold is violated.


The correspondence between record numbers and field names for monitored items

Category

Record number

Field name

Item description

Processor

1052

usrproc

CPU usage in user mode

sysproc

CPU usage in system mode

intproc

UNIX: The time spent waiting for I/O to complete

Windows: The time spent waiting for I/O to be interrupted

totproc

Total CPU usage

Memory

1053

freemem

Available memory

pagins

Page-in count

pagflts

Page fault count

swapused

The ratio of swap or page files being used

pagouts

Page-out count

Disk

1054

dskreads

Number of disk reads

dskwrits

Number of disk writes

kbread

The number of disk reads per kilobyte

kbwritn

The number of disk writes per kilobyte

dsksrvctim

Read/write service time

dskwaittim

Time spent waiting for read/write operations

The information in the table above is resource information relating to the operating system, which is displayed in the Summary window of the Console. Additional items can be monitored with threshold monitoring. In this case, specify the appropriate record numbers and field names by referring to Chapter 4, "Data Formats" in the Reference Guide.