check_weblogic_sessions

nagios plugin to check if a WebAppComponentRuntime object on a weblogic application server is exceeding a maximum specified
concurrent sessions value
author: Sergei Haramundanis 08-Nov-2006

usage: check_weblogic_sessions runtime_directory url userid password object_name maximum_concurrent_sessions

Description:

This plugin will check the concurrent sessions of a WebAppComponentRuntime object with the object_name specified running on a weblogic application server via the weblogic.Admin client

This plugin requires access to weblogic.jar to access the weblogic.Admin client
(see definition of WEBLOGIC_LIB further on in this script, you may need to change it)

This plugin also creates a check_weblogic_sessions.dat file in the runtime_directory specified which contains the snapshot output of all
WebAppComponentRuntime MBean metrics for the weblogic application server at the url specified. The plugin parses this file to extract
the OpenSessionsCurrentCount of the WebAppComponentRuntime MBean which matches the object_name specified in the ObjectName record

Output:

During any run of the plugin, it will poll all WebAppComponentRuntime MBeans on the weblogic application server at the url specified,
writing the output to check_weblogic_sessions.dat and will parse the .dat file for the OpenSessionsCurrentCount of the WebAppComponentRuntime MBean with the ObjectName which matches the pattern in the object_name specified

here is an example of an ObjectName of a weblogic WebAppComponentRuntime object which would be used to match the object_name specified:

ObjectName: weblogic-nd-admin_weblogic-nd-admin_clareon_clareon

Once the plugin finds the correct WebAppComponentRuntime MBean and parses its OpenSessionsCurrentCount it will make the following check:

1. check the OpenSessionsCurrentCount to determine if it is greater than the maximum_concurrent_sessions specified

if the OpenSessionsCurrentCount is less than or equal to the maximum_concurrent_sessions specified it will return an OK state with a message similar to the following example:

[OK] 123 concurrent sessions less than or equal to maximum concurrent sessions of 400

if the OpenSessionsCurrentCount is greater than the maximum_concurrent_sessions specified it will return a CRITICAL state with a message similar to the following example:

[CRITICAL] 438 concurrent sessions greater than maximum concurrent sessions of 400

20-Jun-2007 version 2.1 update includes:
1. support for check_from_time and check_to_time to control monitor timeframe (if you don't want to use this specify values 0000 and 2359)
2. include port # in .dat filename to support monitoring multiple weblogic instances