Page 'monitorplain'

It is possible to monitor Lobster_data and the communication services of the Lobster Integration Server with an external tool (e.g. Nagios).

For this purpose, a servlet or a Java Server Page (JSP) can be provided on request. If you are interested, please contact our support team.

In the simplest case, the JSP file is simply copied into the ./webapps/root directory. The site can then be accessed via HTTP with the following URL.

http://<server>:<port>/monitorplain.jsp

For server and port, the same values are used, as they are entered in the Lobster_data client.

Each HTTP request to monitorplain.jsp provides a response as plain text (MIME type text/plain) in which the monitored properties are listed in a table. The amount of output can be controlled by means of additional query parameters.

Parameter	Description
ftp=true	Show status of FTP service.
smtp=true	Show status of SMTP service.
oftp=true	Show status of OFTP service.
message=true	Show status of Message service.
dw=true	Show status of Lobster_data.
max=true	Only works with all or dw. Shows the currently longest profile runtime.
all=true	Equivalent to ftp=true&smtp=true&oftp=true&message=true&dw=true

Note: The query begins with ?, the parameters are separated by &.

Call

As an example, the following call displays the status of Lobster_data.

http://<server>:<port>/monitorplain.jsp?dw=true

The JSP file is compiled into a servlet when it is invoked the first time, later responses will only take a few milliseconds. Only the parameter max=true (in conjunction with dw=true) consumes more resources and should therefore not be called more than approximately every 10 seconds. If the JSP file can not be compiled on the first call, an HTTP Error 500 appears. This does not have any negative effects on the rest of the components and could be because the file does not match the version of your system. In that case, please contact our support team.

Result

For a parameterless call

http://<server>:<port>/monitorplain.jsp

the status of the main web server and the memory is returned.

Server's local time = Wed Feb 06 10:17:42 CET 2008
HTTP status = Alive
Total memory = 438460 KB
Free memory = 260429 KB
Max memory = 914560 KB
Used memory = 40% used

The maximum information is obtained with the parameter all.

http://<server>:<port>/monitorplain.jsp?all=true

This would, for example, provide a result like the following.

Server's local time = Wed Feb 06 09:24:12 CET 2008
HTTP status = Alive
FTP status = Alive
SMTP status = Alive
OFTP TCP/IP status = Failed -> Connection refused: connect
Message remote interface = Alive
DataWizard status = Alive
DataWizard processed requests = 24657
DataWizard queued jobs = 0
DataWizard queued responses = 0
DataWizard total errors = 61
DataWizard running profiles = 0
Total memory = 438460 KB
Free memory = 283351 KB
Max memory = 914560 KB
Used memory = 35% used

A call with parameter max (only works with all or dw)

http://<server>:<port>/monitorplain.jsp?dw=true&max=true

additionally returns the following line.

DataWizard max job duration = 3203 ms for job 36757