Page History

Wiki Markup\[ZEST:Developing a web-based application which you want ISDA to deploy and monitor?    You should read this entire document, but note especially the bits in red\!\]  

General ISDA Application Server Setup:

...

• the server (usually a linux box running RHEL; whether it's hardware or virtual is immaterial)
• apache (plain and/or SSL), front-ending for one or more instances of...
• apache-tomcat, our servlet container of choice
• the applications themselves

Monitoring Requirements:

Web-based applications deployed for ISDA monitoring services can enjoy the expectation of a stable and monitored servlet container (currently Tomcat) for their use.  Each servlet container must contain a special web application that is specifically designed to monitor all other applications that are deployed to the container.  This special web application will be referred to as the MONITOR for the remainder of this document.  The MONITOR must support service of a standard page retrievable by the URL path: /<container_id>-monitor, where <container_id> is the servlet container identifier.  The content of the response page must satisfy the following criteria:

...

In any case, note that while verbose error messages (example: "FAILURE: backend data server lotsobits.mit.edu is offline") can be helpful for debugging purposes, operational staff response beyond ensuring a functional and health servlet container, restarting the application, and notifying the application developer is on a discretionary and workload-permitting basis.

Critical Monitoring: ("Urgent Response")

...

• per-server, basic: ICMP pingunmigrated-wiki-markup
• per-server, apache health monitoring: a simple Nagios HTTP fetch test of a non-tomcat-served URL, /ping.html \ [ZEST:optional if server is SSL-only\] Wiki Markup
• per-server, apache SSL health monitoring: a imple Nagios HTTPS fetch test of a non-tomcat-served URL, /ping.html \ [ZEST:optional for non-SSL servers\]
• Wiki Markupapplication state monitoring: Nagios HTTP\[ZEST:S\] fetch of */<container_id>-monitor* <span style="color: #ff3300">(see Monitoring Requirements above)</span>

Notes:

• Tomcat and the applications served therefrom are fairly inseperable, rely on the same jvm, and thus share a test, but each server will generally have multiple separate containers for different application groups
• Ideally, this critical reporting functionality will remain unused (see Proactive Status Monitoring below).

Proactive Status Monitoring: ("Impending Doom")

...