Module: check_mk
Branch: master
Commit: 888177cc4e8461374698027659f7303ead508354
URL:
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=888177cc4e8461…
Author: Lars Michelsen <lm(a)mathias-kettner.de>
Date: Tue Jul 26 17:07:54 2011 +0200
Added manpages for some new j4p checks
---
checkman/j4p_performance.threads | 40 ++++++++++++++++++++++++++++++++++++++
checkman/j4p_performance.uptime | 22 ++++++++++++++++++++
2 files changed, 62 insertions(+), 0 deletions(-)
diff --git a/checkman/j4p_performance.threads b/checkman/j4p_performance.threads
new file mode 100644
index 0000000..75c203c
--- /dev/null
+++ b/checkman/j4p_performance.threads
@@ -0,0 +1,40 @@
+title: Check threads of Java application server via JMX and j4p.war
+agents: linux
+author: Lars Michelsen <lm(a)mathias-kettner.de>
+license: GPL
+distribution: check_mk
+description:
+ This checks uses the JSON HTTP service of j4p (from jmx4perl) to
+ monitor the number of threads created by a Java application server like
+ Tomcat or JBoss. You can define levels against the number of threads
+ of the Java machine.
+
+ Take a look at the {j4p_performance.mem} manpage for instructions
+ on how to set up the needed agent plugin.
+
+item:
+ The instance name as configured in {j4p.conf} with the variable
+ {instance}.
+
+examples:
+ # Set default levels for number of threads to (WARN 50, CRIT 80)
+ j4p_performance_threads_default_levels = (50, 80)
+
+perfdata:
+ Several variables:
+ ThreadRate: Number of threads created per interval.
+ ThreadCount: Number of threads.
+ DeamonThreadCount: Number of daemon threads.
+ PeakThreadCount: Maximum number of threads since program start.
+ TotalStartedThreadCount: total number of started threads since program start.
+
+inventory:
+ One check is created for each JMX instance sent by the agent.
+
+[parameters]
+warning (int): The warning level for number of threads
+critical (int): The critical level for number of threads
+
+[configuration]
+j4p_performance_threads_default_levels (int, int): Default levels for number of threads.
+ This is preset to {(80, 100)}.
diff --git a/checkman/j4p_performance.uptime b/checkman/j4p_performance.uptime
new file mode 100644
index 0000000..8575de9
--- /dev/null
+++ b/checkman/j4p_performance.uptime
@@ -0,0 +1,22 @@
+title: Check uptime of Java application server via JMX and j4p.war
+agents: linux
+author: Lars Michelsen <lm(a)mathias-kettner.de>
+license: GPL
+distribution: check_mk
+description:
+ This checks uses the JSON HTTP service of j4p (from jmx4perl) to
+ monitor the uptime of a Java application server like
+ Tomcat or JBoss.
+
+ Take a look at the {j4p_performance.mem} manpage for instructions
+ on how to set up the needed agent plugin.
+
+item:
+ The instance name as configured in {j4p.conf} with the variable
+ {instance}.
+
+perfdata:
+ One variable {uptime} with the uptime in seconds since program start.
+
+inventory:
+ One check is created for each JMX instance sent by the agent.