Service level classifications

Available service level classification options for the HTTP monitor are:

totalTime
lookupTime
connectTime
downloadTime
reponseTime
status
version
server
lastModified
timeSinceModification
bytesTransferred
bytesPerSec
checksum
previousChecksum
percentageDownloadedGood
regexpMatch1 to 3
regexpStatus1 to 3
message

In service level classifications:

• Specify additional service level classifications by manually entering the name of the monitor element. The name must match the name shown for the element in the Monitor elements section.
• message can be any message forwarded in the $message element to IBM Tivoli Monitoring or, if applicable, to the Netcool/OMNIbus ObjectServer. For a list of possible values, see Status messages.
• The operand is a string or a positive number.
• status codes 200, 301, and 302 indicate success. See the HTTP protocol for other status codes returned by the operation.
• regexpStatusn may have the following values:
  • NONE: No regular expression checking is configured
  • MATCHED: A match was found for the regular expression
  • FAILED: A match was not found for the regular expression
• Evaluate regular expression matches using test expressions of the format:

  regexpMatchn [contains|!contains] expression 

  Use contains and !contains operators in place of = and != because regexpMatchn normally contains the entire line matching the regular expression instead of just the matching portion, so the = and != operators often do not match the expression.

• The Checksum and PreviousChecksum elements do not normally provide meaningful values for service level classifications because checksum values are not known when the profile element is created (the monitor calculates checksum values while tests are in progress). The $checksum and $previousChecksum monitor elements are intended for alert enrichment using the monitor's rules file.