HTTP Device Driver allows AggreGate Server to monitor web servers and web pages (URLs).
|
A web server is a computer program that delivers (serves) content, such as web pages, using the Hypertext Transfer Protocol (HTTP), over the World Wide Web. |
HTTP driver provides monitoring of any web server (Apache, IIS, etc.) by checking whether a monitored device accepts HTTP requests and responds with correct pages. The driver supports GET and POST requests, authorization and other options for HTTP requests.
Driver Information
Driver Plugin ID: |
com.tibbo.linkserver.plugin.device.http |
Global Settings
None defined.
User Level Settings
None defined.
Device Properties
Connection Properties
Connection settings define how AggreGate Server communicates with a certain HTTP server. These settings can be accessed using Edit Device Properties action of the Device Context. Here is a list of available connection properties:
Setting |
Description |
||||
Address |
IP address or host name of the HTTP server. |
||||
Port |
Port the HTTP server is running on. |
||||
URL |
Path to a monitored resource located on the specified HTTP server. |
||||
Request Type |
Two HTTP request methods are currently supported: GET and POST. |
||||
Post Data |
Data to be submitted with POST request, in the string form. |
||||
Enable Authorization |
Enables realm authorization (if it's required). |
||||
Username |
User name to be used for authorization. |
||||
Password |
Password for authorization. |
||||
Additional HTTP Headers |
Additional information to be included in request header. Specified as a table with the following fields:
|
||||
Agent |
User agent string. |
||||
Timeout |
HTTP server operations timeout. |
Device Settings
HTTP device driver creates the only Device setting variable indicating the result of HTTP request. This variable includes the following fields that may be analyzed using different AggreGate modules:
Property |
Description |
Successful |
Indicates that web server monitor had no error during last page read. |
Response Time, milliseconds |
Server response time. |
Reply Code |
HTTP response code. |
Headers |
HTTP response headers table. |
Reply |
HTTP response body, i.e. web page contents. |
Error |
Error text, or NULL if request was successful (even if HTTP response code is not 200/OK). |
Device Operations
No operations provided by the driver.
Device Events
No events provided by the driver.
Connection Handling
HTTP device is deemed Online if no error occurred during connection and HTTP request execution, and valid HTTP response was obtained.
Synchronization Details
HTTP monitor connects to the IP host, sends an HTTP request built using provided configuration (port, URL, request type and data, HTTP headers, agent, timeout) and analyzes the response.
|
If authentication is enabled in the settings and Basic Access Authentication is required to access a web page the driver also sends an authorization request. |
