# PageSequenceMonitor

The PageSequenceMonitor (PSM) lets OpenNMS monitor web applications. This monitor has several configuration options regarding IPv4, IPv6, and how to deal with name resolution. To add flexibility, the node label and IP address can be passed as variables into the monitor. This lets you run the monitor with node-dependent configuration. Beyond testing a web application with a single URL, it can also test a path through a web application. A test path through an web application can look like this:

2. Run an action while logged in.

3. Log off.

The service is considered as up if all the steps in the sequence return valid responses. If there is an error somewhere, your application will need attention and the service changes the state to down.

## Monitor facts

 Class Name `org.opennms.netmgt.poller.monitors.PageSequenceMonitor`

## Configuration and use

The configuration for this monitor consists of several parts. First is the overall configuration for retries and timeouts. These parameters are global for the whole path throughout the web application.

Figure 1. Configuration overview of the PageSequenceMonitor

The overall layout of the monitor configuration is more complex than other service monitors. It is possible to configure a page sequence that contains a path through a web application by checking multiple pages in succession.

Table 1. Monitor-specific parameters for the PageSequenceMonitor
Parameter Description Default

Required

page-sequence

Definition of the page sequence to run. See table below with page sequence parameters.

n/a

Optional

retry

The number of retries per page.

0

strict-timeout

Number of milliseconds to wait before retrying. Used only if the retry parameter is not set to zero.
If `retry >= 1` and `strict-timeout` is `true`, the next attempt is delayed and the Poller daemon waits `NOW - InitialAttempt ms + Timeout ms`.
With `strict-timeout = false` the next attempt starts right after a failure.

false

sequence-retry

The retry parameter for the entire page sequence.

0

use-system-proxy

Should the system-wide proxy settings be used? Configure the system proxy settings via system properties.

false

This monitor implements the Common Configuration Parameters.

Table 2. Page parameters
Parameter Description Default

Required

path

The relative URL to call in the request. Any query string content after a `?` should be part of the query parameter.

n/a

Optional

name

The name of the page-sequence.

n/a

method

HTTP method (GET or POST)

n/a

http-version

HTTP protocol version (0.9, 1.0, or 1.1)

HTTP/1.1

user-agent

Set the user agent field in the HTTP header to identify the OpenNMS monitor.

OpenNMS PageSequenceMonitor (Service name: "${SERVICE NAME}") virtual-host Set the virtual host field in the HTTP header. In case of an HTTPS request, this is also the virtual domain to send as part of the TLS negotiation, known as server name indication (SNI) (See: RFC3546, section 3.1.). n/a scheme Define the URL scheme as http or https. http user-info Set user info field in the HTTP header. Colon-separated credentials such as USERNAME:PASSWORD. n/a host Set host field in HTTP header. IP interface address of the service requireIPv6 Communication requires a connection to an IPv6 address (true or false). n/a requireIPv4 Communication requires a connection to an IPv4 address (true or false) n/a disable-ssl-verification Enable or disable SSL certificate verification for HTTPS tests. Use this option carefully, since self-signed certificates import the CA certificate in the JVM and do not just disable it. false port Host port number to use when connecting. 80 query Value to concatenate with a `?` after the path parameter. n/a failureMatch Text to look for in the response body. This is a regular expression matched against every line, is considered a failure at the first match, and sets the service with this monitor as Down. n/a failureMessage The failure message constructs the reason code. Use `${n}` values to pull information from matching groups in the failureMatch regular expression.

n/a

successMatch

Text to look for in the response body. This is a regular expression matched against every line, is considered a success at the first match, and sets the service with this monitor as Up.

n/a

locationMatch

The relative URL that must be located for the request to be successful.

n/a

response-range

Range for allowed HTTP error codes from the response.

n/a

session-variable

Assign the value of a regex match group to a session variable with a user-defined name. The match group is identified by number and must be zero or greater.

n/a

response-range

A comma-separated list of acceptable HTTP response code ranges (200-202,299).

100-399

 If you set both `requireIPv4` and `requireIPv6` to false, the host IP for connection will be resolved from system name resolver and the associated IP address from the IP interface is ignored.

## Session variables

It is possible to assign strings from a retrieved page to variables that can be used in page parameters later in the same sequence. First, specify one or more capturing groups in the successMatch expression (see Java Class Pattern for more information on regular expressions in Java). Use the session-variable parameter to assign the captured values to variable names for use in a later page load.

## Per-page response times

To collect response times for individual pages in a sequence, add a ds-name attribute to each page whose load time should be tracked. The response time for each page will be stored in the same RRD file specified for the service via the rrd-base-name parameter under the specified data source name.

 You need to delete existing RRD files and let them be recreated with the new list of data sources when you add a ds-name attribute to a page in a sequence that is already storing response-time data.

## Examples

The following example shows how to monitor the OpenNMS web application using several mechanisms.

It first does an HTTP GET of `http://${ipaddr}:8980/opennms/login.jsp` (following redirects as a browser would) and then checks to ensure that the resulting page has the phrase `Password` on it. Next, it uses HTTP POST to attempt a login to the relative URL for submitting form data (usually the URL that the form action points to). The parameters (`j_username` and `j_password`) indicate the form’s data and values to submit. Furthermore, it sets a custom header (`foo`) for demonstration purposes. After getting the resulting page, the expression specified in the page’s failureMatch attribute is verified, which when found anywhere on the page indicates that the page has failed. If the failureMatch expression is not found in the resulting page, then the expression specified in the page’s successMatch attribute is checked to ensure it matches the resulting page. If the successMatch expression is not found on the page, then the page fails. If the monitor was able to successfully log in, then the next page is processed. In the example, the monitor navigates to the Event page, to ensure that it finds the text "Event Queries" on the page. Finally, the monitor calls the URL of the logout page to close the session. Using the locationMatch parameter verifies that the logout was successful and a redirect was triggered. Each page is checked to ensure its HTTP response code fits into the response-range, before the failureMatch, successMatch, and locationMatch expressions are evaluated. Example uses CentOS/RHEL path name. For Debian/Ubuntu, use `/var/lib/opennms/rrd/response`. Note that you must include the `monitor` section for each service in your definition. Configuration to test the login to the Meridian web application ``````<service name="OpenNMS-Web-Login" interval="30000" user-defined="true" status="on"> <parameter key="retry" value="1"/> <parameter key="timeout" value="5000"/> <parameter key="rrd-repository" value="/opt/opennms/share/rrd/response"/> <parameter key="ds-name" value="opennmslogin"/> <parameter key="page-sequence"> <page-sequence> <page path="/opennms/login.jsp" (1) port="8980" (2) successMatch="Password" /> (3) <page path="/opennms/j_spring_security_check" (1) port="8980" (2) method="POST"> (4) <parameter key="j_username" value="admin"/> <parameter key="j_password" value="admin"/> <header name="foo" value="bar"/> </page> <page path="/opennms/index.jsp" (1) port="8980" (2) successMatch="Log Out" /> (3) <page path="/opennms/event/index" (1) port="8980" (2) successMatch="Event Queries" /> (3) <page path="/opennms/j_spring_security_logout" (1) port="8980" (2) method="POST" (4) response-range="300-399" (5) locationMatch="/opennms" /> (6) </page-sequence> </parameter> </service> <monitor service="OpenNMS-Web-Login" class-name="org.opennms.netmgt.poller.monitors.PageSequenceMonitor"/> (7)``````  1 The relative URL to call in the request. 2 Host port number to use when connecting. 3 Text to look for in the response body. 4 HTTP method (GET or POST). 5 Range for allowed HTTP error codes from the response. 6 The relative URL that must be located for the request to be successful. 7 Required monitor section. Test with mixing HTTP and HTTPS in a page sequence ``````<service name="OpenNMS-Web-Login" interval="30000" user-defined="true" status="on"> <parameter key="retry" value="1"/> <parameter key="timeout" value="5000"/> <parameter key="rrd-repository" value="/opt/opennms/share/rrd/response"/> <parameter key="ds-name" value="opennmslogin"/> <parameter key="page-sequence"> <page-sequence> <page scheme="http" (1) host="ecomm.example.com" (2) port="80" (3) path="/ecomm/jsp/Login.jsp" (4) virtual-host="ecomm.example.com" (5) successMatch="eComm Login" (6) timeout="10000" (7) http-version="1.1"/> (8) <page scheme="https" (1) method="POST" (9) host="ecomm.example.com" port="443" (2) path="/ecomm/controller" (4) virtual-host="ecomm.example.com" (5) successMatch="requesttab_select.gif" (6) failureMessage="Login failed:${1}" (10)
timeout="10000" (7)
http-version="1.1"> (8)
<parameter key="action_name"
<parameter key="session_timeout"
value=""/>
<parameter key="userid"
value="EXAMPLE"/>
value="econ"/>
</page>
<page scheme="http" (1)
host="ecomm.example.com" (2)
port="80" (3)
path="/econsult/controller" (4)
virtual-host="ecomm.example.com" (5)
successMatch="You have successfully logged out of eComm" (6)
timeout="10000" (7)
http-version="1.1"> (8)
<parameter key="action_name"
value="XbtnLogout"/>
</page>
</page-sequence>
</parameter>
</service>

 1 Define the URL scheme as http or https. 2 Set host field in HTTP header. 3 Host port number to use when connecting. 4 The relative URL to call in the request. 5 Set the virtual host field in the HTTP header. 6 Text to look for in the response body. 7 Timeout for the isReachable method, in milliseconds. 8 HTTP protocol version (0.9, 1.0, or 1.1). 9 HTTP method (GET or POST). 10 The failure message constructs the reason code. 11 Required monitor section.
Test login with dynamic credentials using session variables
``````<service name="OpenNMS-Web-Login" interval="30000" user-defined="true" status="on">
<parameter key="retry" value="1"/>
<parameter key="timeout" value="5000"/>
<parameter key="rrd-repository" value="/opt/opennms/share/rrd/response"/>
<parameter key="page-sequence">
<page path="/opennms" (2)
port="80" (3)
virtual-host="demo.opennms.org" (4)
match-group="1" />
match-group="2" />
</page>
<page path="/opennms/j_acegi_security_check" (2)
port="80" (3)
virtual-host="demo.opennms.org" (4)
method="POST" (6)
failureMessage="Login Failed: ${1}" (8) successMatch="Log out">" (5) <parameter key="j_username" value="${username}" />
value="${password}" /> </page> <page path="/opennms/event/index.jsp" (2) port="80" (3) virtual-host="demo.opennms.org" (4) successMatch="Event Queries" /> (5) <page path="/opennms/j_acegi_logout" (2) port="80" (3) virtual-host="demo.opennms.org" (4) successMatch="logged off" /> (5) </page-sequence> </parameter> </service> <monitor service="OpenNMS-Web-Login" class-name="org.opennms.netmgt.poller.monitors.PageSequenceMonitor"/> (9)``````  1 The name of the page sequence. 2 The relative URL to call in the request. 3 Host port number to use when connecting. 4 Set the virtual host field in the HTTP header. 5 Text to look for in the response body. 6 HTTP method (GET or POST). 7 Text to look for in the response body. 8 The failure message constructs the reason code. 9 Required monitor section. Log in to `demo.opennms.org` without knowing username and password ``````<service name="OpenNMS-Demo-Login" interval="300000" user-defined="true" status="on"> <parameter key="page-sequence"> <page-sequence> <page path="/opennms" (1) port="80" (2) virtual-host="demo.opennms.org" (3) successMatch="(?s)User:.*<strong>(.*?)</strong>.*?Password:.*?<strong>(.*?)</strong>"> (4) <session-variable name="username" match-group="1" /> (5) <session-variable name="password" match-group="2" /> (6) </page> <page path="/opennms/j_acegi_security_check" (1) port="80" (2) virtual-host="demo.opennms.org" (3) method="POST" (7) successMatch="Log out">" (4) <parameter key="j_username" value="${username}" />
</page>
<page path="/opennms/j_acegi_logout" (1)
port="80" (2)
virtual-host="demo.opennms.org" (3)
successMatch="logged off" /> (4)
</page-sequence>
</parameter>
</service>

 1 The relative URL to call in the request. 2 Host port number to use when connecting. 3 Set the virtual host field in the HTTP header. 4 Text to look for in the response body. 5 Assign the value of a regex match group to a session variable. 6 Assign the value of a regex match group to a session variable (in this case, password). 7 HTTP method (GET or POST). 8 Required monitor section.
Example with per-page response times
``````<service name="OpenNMS-Login" interval="300000" user-defined="false" status="on">
<parameter key="rrd-repository" value="/opt/opennms/share/rrd/response"/>
<parameter key="ds-name" value="overall"/>
<parameter key="page-sequence">
<page-sequence>