Page History

...

FTP

The FTP monitor can determine:

whether an FTP server is listening or is available on a specified port
the response time of an FTP server

The FTP monitor tries to open an FTP connection to the server. If the response takes longer than the defined thresholds, Uptime Infrastructure Monitor generates an alert.

Configuring FTP Monitors

To configure FTP monitors, do the following:

In the FTP monitor template, complete the monitor information fields.
To learn how to configure monitor information fields, see Monitor Identification.
Complete the following fields:
- Port
  The number of the port number on which the FTP server is listening. The default is 21.
- Server Response
  Enter the Warning and Critical time thresholds required to receive a ready response from the FTP server. A server ready response can look like the following:
  220 filter FTP server (Version wu-2.6.2(1) Mon Thurs Dec 3 15:29:55 EST 20052015) ready
- For more information, see Configuring Warning and Critical Thresholds.
- Response Time
  Enter the Warning and Critical Response Time thresholds for the length of time that the service check takes to complete. For more information, see Configuring Warning and Critical Thresholds.
Click the Save for Graphing checkbox to save the data for a metric to the DataStore, which can be used to generate a report or graph.
Complete the following settings:
- Timing Settings (see Adding Monitor Timing Settings Information for more information)
- Alert Settings (see Monitor Alert Settings for more information)
- Monitoring Period settings (see Monitor Timing Settings for more information)
- Alert Profile settings (see Alert Profiles for more information)
- Action Profile settings (see Action Profiles for more information)
Click Finish .

HTTP (Web Services)

The HTTP (Web Services) monitor simulates the steps that you take to access a Web site. Using this monitor, you can verify several things:

you can access a Web site using HTTP
you can log on to a Web site
a Web site is running according to your expectations

You can determine this by examining the values that are returned from the Web server.

The HTTP (Web Services) monitor relies on a Universal Resource Identifier (URI), which defines a specific file location on a Web server. This monitor can test for application calls, database responses, or any other information that a URI can return.

Configuring HTTP (Web Services) Monitors

To configure HTTP (Web Services) monitors, do the following:

In the HTTP (Web Services) monitor template, complete the monitor information fields.
To learn about monitor information fields, see Monitor Identification.
Complete the following fields:
- URI
  The URI of the Web page that you want to monitor. For example,
  /login.php .
- Text to Look For (Optional)
  Enter the text that you want the monitor to search for in the response from the server.
  This monitor parses the text from the server and, using the threshold values you enter, determines if the entire Web page returned by the server is within acceptable parameters.
  For example, if a Web page is returned then the monitor parses the entire page for the text that you input to match against. If you want to ensure that a particular page is returned, you could enter <TITLE>Expected Page</TITLE> , where Expected Page is the title of the Web page. The monitor generates an alert if this page is not matched.
- Authentication
  The user ID and password, in the form userid:password. For example:
  jlamport:bluefrog5
- Virtual Host
  The unique domain name that resolves to the IP address of the domain that you want to monitor. A virtual host has its own domain name, but has the same IP address as other domain names hosted by the Web server.
- Server Response
  Enter a string to match against the response from the server. For example, HTTP/1.1 200 OK or HTTP 404 - File not found . Then, set the Warning and Critical comparison methods. For more information, see Configuring Warning and Critical Thresholds
- Follow Redirect Actions
  Select an action that enables you to specify whether you want to be redirected to another Web address:
  - OK
    Return an OK status for any re-direction.
  - Follow
    Follow any re-direction.
  - Warning
    Return a Warning status for any re-direction.
  - Critical
    Return a Critical status for any re-direction.
- POST String
  The URL-encoded POST string to be sent to the server. This string simulates what a Web browser sends to a Web server CGI script or binary. You can use the POST string to, for example, simulate logging into a Web application.
  For example, if you define the POST string as userid=bob &sku=123456 , the page to request would be /cgi-bin/sku_lookup . The text “ SKU count is ” is the expected response. If the SKU lookup is not successful or if the response from the application server is not fast enough, then Uptime Infrastructure Monitor generates an alert.
- Set-Cookie String
  The parameters that define the cookie. The cookie string uses the following format:
  domain:name:value:path
  If configuring multiple cookies for the monitor, separate each cookie string with a semicolon:
  - domain is the subdomain the cookie is available to.
  - name is a name with which you can later reference the cookie.
  - value is a regular string to be stored as a cookie. The string should be encoded using URL-style %xx encoding, which converts all reserved and unsafe characters - such as tildes (~) and spaces - to their ASCII equivalents.
    For example, using %xx encoding, the URL http://www.mydomain.com/~jdoe/index.html becomes http://www.mydomain.com/%7ejdoe/index.html path is the location on the server in which the cookie is made available. For example, if the path is “ / ” the cookie is available to the entire domain, as opposed to a specific subdirectory name.
    d1:n1:v1:p1;d2:n2:v2:p2
    The name and value pair is the only required attribute of the Set-Cookie String field.
- HTTP Header Settings
  The HTTP header settings for the response.
  The HTTP header settings define the syntax and semantics of all standard HTTP/1.1 header fields. For entity header fields, both sender and recipient refer to either the client or the server, depending on who sends and who receives the entity.
- Response Time
  Enter the Warning and Critical Response Time thresholds. For more information, see Configuring Warning and Critical Thresholds
Click the Save for Graphing checkbox to save the data for a metric to the DataStore, which can be used to generate a report or graph.
Complete the following settings:
- Timing Settings (see Adding Monitor Timing Settings Information for more information)
- Alert Settings (see Monitor Alert Settings for more information)
- Monitoring Period settings (see Monitor Timing Settings for more information)
- Alert Profile settings (see Alert Profiles for more information)
- Action Profile settings (see Action Profiles for more information)
Click Finish.

IMAP (Email Retrieval)

The IMAP (Email Retrieval) monitor confirms whether an IMAP server is doing the following:

listening on a defined port
running on a defined system or on a group of systems
using a particular version

Configuring IMAP (Email Retrieval) Monitors

To configure IMAP (Email Retrieval) monitors, do the following:

In the IMAP (Email Retrieval) monitor template, complete the monitor information fields.
To learn how to configure monitor information fields, see Monitor Identification.
Complete the following fields:
- Port
  The number of the port on which IMAP is listening.
  The default is 143 . If you are applying a monitor to a service group, ensure that all of the systems use the defined port. Otherwise, create a monitor for each IMAP instance that listens on a different port.
  For information on service groups, see Service Groups.
- Server Response
  Select a comparison method, and then enter the Warning and Critical thresholds for the server response. For more information, see Configuring Warning and Critical Thresholds.
  The server response is the same for Windows, UNIX, and Linux. For example, an expected response is:
  No Format
  nopanel true
  +OK [CAPABILITY IMAP4REV1 LOGIN-REFERRALS STARTTLS AUTH=LOGIN] filter IMAP4rev1 2002.336 at ThuTue, 2 Jun 2005 10:55:02 -400 (EDT)
  If IMAP is not available, then the following is an expected response:
  No Format
  nopanel true
  BAD Null command
  By making string comparisons on the returned values to the monitor, you can check:
  - The version of IMAP that is running to support your network routing.
  - The system on which IMAP is or is not running.
- Response Time
  Enter the Warning and Critical Response Time thresholds for the length of time a service check takes to complete. For more information, see Configuring Warning and Critical Thresholds.
Click the Save for Graphing checkbox to save the data for a metric to the DataStore, which can be used to generate a report or graph.
Complete the following settings:
- Timing Settings (see Adding Monitor Timing Settings Information for more information)
- Alert Settings (see Monitor Alert Settings for more information)
- Monitoring Period settings (see Monitor Timing Settings for more information)
- Alert Profile settings (see Alert Profiles for more information)
- Action Profile settings (see Action Profiles for more information)
Click Finish.

...

TCP

The TCP monitor can determine whether a service or application is listening on a specific port. This monitor can also execute commands against an application or a service listening on a port and evaluate the result.

By extending the TCP monitor to evaluate the returned string based on a command over a network using TCP, you can test and monitor for a wide variety of responses.

For example, to have Uptime Infrastructure Monitor generate an alert if the file Weekly_Report was changed in your source code control system, you can send the string:

No Format

nopanel	true

get -e Weekly_Report1

and set the critical threshold value to 1.2 , where 1.1 represents no changes and 1.2 or greater represents one or more changes to the document.

Configuring TCP Monitors

To configure TCP monitors, do the following:

In the TCP monitor template, complete the monitor information fields.
To learn how to configure monitor information fields, see Monitor Identification.
Complete the following fields:
- Port
  The number of the port on which the service or application that you want to monitor is listening.
  Info
  To check whether an application is listening on a port, leave the remaining TCP service monitor settings blank.
- String to Send
  The string that contains the command to which the service or application can respond.
- Use SSL
  Select this option if your connection uses SSL (Secure Sockets Layer) for security.
- String to Receive
  The string that is returned by the specified port and host. The string is the response to the command that was specified in the String to Send field.
- Response Time
  Enter the Warning and Critical Response Time thresholds. For more information, see Configuring Warning and Critical Thresholds.
Click the Save for Graphing checkbox to save the data for a metric to the DataStore, which can be used to generate a report or graph.
Complete the following settings:
- Timing Settings (see Adding Monitor Timing Settings Information for more information)
- Alert Settings (see Monitor Alert Settings for more information)
- Monitoring Period settings (see Monitor Timing Settings for more information)
- Alert Profile settings (see Alert Profiles for more information)
- Action Profile settings (see Action Profiles for more information)
Click Finish.

Save

Page tree

Versions Compared

Old Version 6

New Version Current

Key

FTP