Common monitor elements
This section describes the elements produced by all monitors. Monitor specific elements are described in the individual monitor sections. Produced elements can be viewed in the Internet Service Monitoring Agent dashboard.
If you use IBM® Application Performance Management, the elements that can be viewed on the agent's dashboard as attributes are determined by a mapping file generated by the Internet service monitoring agent. This mapping file isn’t configurable.
|
Element name |
Element description |
|---|---|
|
|
If If, at this poll, the service level is passed or starts increasing again, the element is no
longer created. If the value of this element exceeds the value of Note: The TRANSX monitor doesn’t generate this element.
|
|
( |
The path to the datalog file used by the monitor. The workspace attribute uses the last 100 characters of the path. |
|
( |
Contains the text description provided in the Description field of the monitor profile element. |
|
|
The poll interval used during failure retesting. This is only valid if
Note: The TRANSX monitor doesn’t generate this element.
|
|
|
The number of service level failures that has to be exceeded before a failed event is recorded and sent to the ObjectServer. Note: The TRANSX monitor doesn’t generate this element.
|
|
( |
The name of the host or server. Stored in the configuration file. |
|
|
Contains the host name of the |
|
|
Contains the host IP of the |
|
( |
The identifier of the profile element. |
|
( |
The service level number of the previous poll. This is cleared if the profile changes. |
|
|
The |
|
|
The domain name of the machine running the monitor, as used by DNS. |
|
( |
The name of the host running the monitor. |
|
|
The domain name of the host running the monitor, as used by NIS (Network Information Service). |
|
|
Overrides the |
|
( |
A text string describing the result of the poll. For example, |
(Node) |
The name of the system on which Internet Service Monitoring is running. This attribute is added by the Internet service monitoring agent. |
|
|
The poll interval specified in each monitor. |
|
( |
A text string indicating the service level classification applied to the results of the poll. For
example, |
|
( |
The name of the service being monitored. For example, |
|
( |
The service level number of the poll, as defined in the service level classification:
|
|
|
The number of times that the service level number has remained unchanged. |
(ServiceLevelString) |
The string associated with the returned service level (Unknown,
Good, Marginal, or Failed). |
|
|
The time when the poll started. |
|
|
The UNIX time, in seconds, when the poll occurred. |
|
( |
The date and time when the test was performed. The timestamp format uses local settings. |
|
|
The name of the transaction. This is produced by a monitor if the monitor is used in a transaction. |
|
Profile Details |
|
|
( |
The name of the user profile. |
|
Timings - for information about how timings are measured, see Time Calculations. |
|
|
|
The number of seconds in which the server must respond. Taken from the configuration file. |
|
( |
The total time taken to run an operation in seconds. This includes all lookup, connect, and download times where applicable, and interim processing time. |
Time Calculations
Monitors attempt to divide the time taken to complete a poll into different timed stages. For example, this could include the time taken to obtain a host's IP address, or the time taken to successfully connect to a host.

The $totalTime is always slightly longer than the sum of the other times, because it includes the overhead incurred by the monitor's activities such as processing received data and performing system calls. $totalTime is measured in seconds.