Internet Service Monitoring reference
The core components of Internet Service Monitoring are
the monitors, which test the availability and performance of an Internet
service.
DHCP monitor
The DHCP monitor checks the availability and response time of DHCP
servers.
DNS monitor
The DNS monitor uses the DNS (Domain Name System) service
to find information about one or more hosts.
FTP monitor
The FTP monitor tests FTP services by either uploading files to,
or downloading files from FTP servers. It monitors the performance of the
service by recording the response time and data transfer rate, and monitors
disk space and file integrity.
HTTP monitor
The HTTP monitor checks the availability and response time
of web servers.
HTTPS monitor
The HTTPS monitor checks the availability and response
time of web servers. It can monitor individual web pages, including
those that use HTML forms which normally require the user to enter
data into fields.
ICMP monitor
The ICMP monitor tests the performance of the Internet
Control Message Protocol service running on a network. To do this,
the monitor uses the ICMP echo command.
IMAP4 monitor
The IMAP4 monitor works in conjunction with the SMTP monitor to
test the availability and response time of an IMAP4 e-mail service.
LDAP monitor
The LDAP monitor tests the operation of Lightweight Directory Access
Protocol (LDAP) servers.
NNTP monitor
The NNTP monitor tests the availability of an NNTP service by reading
from and posting to a newsgroup.
NTP monitor
The Network Time Protocol (NTP) monitor queries an NTP server using
UDP (User Datagram Protocol) to determine whether the server is supplying
the correct time.
POP3 monitor
The POP3 monitor works in conjunction with the SMTP monitor to
test the availability and response time of a POP3 e-mail service.
RADIUS monitor
Remote Authentication Dial-In User Service (RADIUS) provides authentication
for remote access to services. The RADIUS monitor simulates a client system
accessing a RADIUS service and returns data about the performance of the service.
RPING monitor
The RPING monitor tests the availability of network devices by
pinging them remotely from a router. It provides maximum, minimum, and average
round trip time performance data.
RTSP monitor
The Real Time Streaming Protocol (RTSP) monitor tests audio and
video stream playback on streaming servers. It gathers information about media
files, and initiates stream playback, pause, and the end of a streaming session.
SAA monitor
The Cisco Service Assurance Agent (SAA) is a performance monitoring
agent for Cisco products using IOS version 12.2(2) and above.
SIP monitor
The SIP monitor checks the availability of Session Initiation Protocol
(SIP) servers, including the time taken to register and authenticate end points.
The monitor initiates a SIP session so that SIP requests and SIP responses
can be monitored.
SMTP monitor
The SMTP monitor works in conjunction with the IMAP4 or POP3 monitors
to test the performance of an e-mail service.
SNMP monitor
The SNMP monitor tests SNMP-enabled devices for performance
and fault data.
SOAP monitor
The SOAP monitor checks the availability and response
time of the SOAP interface (SOAP 1.0 and 1.1). It can also monitor
the validity of SOAP inputs (requests) and SOAP outputs (responses).
TCPPort monitor
The TCPPort monitor provides coverage for services not tested by
the other monitors. It detects and responds to commands or strings on a TCP
port. This monitor is particularly useful for monitoring bespoke services.
TFTP monitor
The TFTP monitor measures the performance of the Trivial File Transfer
Protocol (TFTP) service between two systems.
TRANSX monitor
The TRANSX monitor simulates the actions of a real Internet
user by executing a series of activities, which it performs using
other Internet service monitors.
Internet Service Monitoring command-line interface
You can use either the Internet Service Monitoring Configuration
command-line interface or ismbatch command
on the command-line. The commands for both are similar and are described
in this section.
Regular expression syntax
Regular expressions perform string matching on content downloaded
during service tests. These expressions may contain one or more regular expression
operators, which determine what content is matched by the expression.
Summary of RFCs
The protocols underlying many of the Internet services
that you can monitor with Internet Service Monitoring are
formally defined in Internet Engineering Task Force (IETF) Request
For Comment (RFC) documents.
ttdla.xsd schema
You use the Transaction Tracking Discovery Library Adapter
(TTDLA) to generate iDML books suitable for use by Tivoli Business Service Manager. The
TTDLA takes XML data extracted from Transaction Tracking and
generates a document for further transformation. This document structure
is defined by the ttdla.xsd schema.
Internet Service Monitoring directory structure Internet Service Monitoring installs
to a subdirectory of the ITM directory structure, known as ISMHOME.
On Windows systems, ISMHOME is c:\IBM\ITM\tmaitm6\ism;
on Linux and UNIX systems
it is /opt/IBM/ITM/arch/is.
Instrumenting Application Response Measurement
The Application Response Measurement (ARM) API is a set
of standard API calls that enable you to measure the performance of
your applications.
ADO.NET supported namespaces
The following table lists the ADO.NET client side APIs
that are monitored by the .NET Data Collector.
Transport address format
This appendix provides definitions of the available addressing
schemes for connecting an instrumented application to a Transaction Collector.
Return codes Transaction Tracking API functions
return values in a return code – a fullword area.
The kto_stitching file
The kto_stitching.xml file defines
how horizontal and vertical stitching occurs for events. It consists
of definitions for Stitch Pairs.