[Tomcat Wiki] Update of "FAQ/Monitoring" by ChristopherSchultz
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Tomcat Wiki" for change
notification.
The "FAQ/Monitoring" page has been changed by ChristopherSchultz:
http://wiki.apache.org/tomcat/FAQ/Monitoring?action=diff&rev1=9&rev2=10
Comment:
Added information about ThreadPool.
{{{#!wiki caution
Version Warning
- These JMX bean names are accurate for the current version of Tomcat 7 (7.0.28
at the time of this writing). If you are using a different version of Tomcat,
you may have to adjust the names of the beans identified on this page.
+ These JMX bean names are accurate for the current version of Tomcat 7 (7.0.37
at the time of this writing). If you are using a different version of Tomcat,
you may have to adjust the names of the beans identified on this page.
}}}
=== Thread Usage ===
@@ -38, +38 @@
* Attributes: `poolSize`, `activeCount`
This is the number of threads currently in the executor's thread pool.
Obviously, this is only useful if you are using an (which you
''are'' using, of course, right?).
+
+ Not using an Executor
+
+ * JMX Bean: `Catalina: type=ThreadPool,name="[depends]"`
+ * Attributes: `maxThreads`, `connectionCount`
+
+ This information is largely useless in Tomcat 7, as an Executor is always
used and the data can be found there, while the ThreadPool has only initial
configuration information: the real-time data is available from the Executor's
MBean.
=== Request Throughput ===
@@ -48, +55 @@
=== Sessions ===
* JMX Bean: `Catalina:type=Manager,context=[context name],host=[hostname]`
+ * Attributes: `activeSessions`, `sessionCounter`, `expiredSessions`
- * Attributes: `activeSessions`
-
=== JNDI DataSource ===
- * JMX Bean: `Catalina:type=DataSource,context=/[context
name],host=[hostname],class=javax.sql.DataSource,name="[JNDI name]"`
+ * JMX Bean: `Catalina:type=DataSource,context=[context
name],host=[hostname],class=javax.sql.DataSource,name="[JNDI name]"`
* Attributes: `numActive`, `numIdle`
= External Monitoring Tools =
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[Tomcat Wiki] Update of "FAQ/Monitoring" by ChristopherSchultz
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tomcat Wiki" for change notification. The "FAQ/Monitoring" page has been changed by ChristopherSchultz: http://wiki.apache.org/tomcat/FAQ/Monitoring?action=diff&rev1=7&rev2=8 Comment: Added JNDI DataSource JMX Bean and attributes * JMX Bean: `Catalina:type=Manager,context=[context name],host=[hostname]` * Attributes: `activeSessions` + + === JNDI DataSource === + + * JMX Bean: `Catalina:type=DataSource,context=/[context name],host=[hostname],class=javax.sql.DataSource,name="[JNDI name]" + * Attributes: `numActive`, `numIdle` + = External Monitoring Tools = Plug-in-based monitoring software like Nagios and Icinga may need some help interacting with Tomcat's JMXProxyServlet. [[tools/check_jmxproxy.pl]] is a Perl script that can be used with these tools to monitor Tomcat via the JMXProxyServlet. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Tomcat Wiki] Update of "FAQ/Monitoring" by ChristopherSchultz
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tomcat Wiki" for change notification. The "FAQ/Monitoring" page has been changed by ChristopherSchultz: http://wiki.apache.org/tomcat/FAQ/Monitoring?action=diff&rev1=5&rev2=6 = External Monitoring Tools = - Plug-in-based monitoring software like Nagios and Icinga may need some help interacting with Tomcat's JMXProxyServlet. [[check_jmx]] is a Perl script that can be used with these tools to monitor Tomcat via the JMXProxyServlet. + Plug-in-based monitoring software like Nagios and Icinga may need some help interacting with Tomcat's JMXProxyServlet. [[tools/check_jmx]] is a Perl script that can be used with these tools to monitor Tomcat via the JMXProxyServlet. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Tomcat Wiki] Update of "FAQ/Monitoring" by ChristopherSchultz
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tomcat Wiki" for change notification. The "FAQ/Monitoring" page has been changed by ChristopherSchultz: http://wiki.apache.org/tomcat/FAQ/Monitoring?action=diff&rev1=4&rev2=5 = External Monitoring Tools = - Plug-in-based monitoring software like Nagios and Icinga may need some help interacting with Tomcat's JMXProxyServlet. [[attachment:check_jmx|check_jmx]] is a Perl script that can be used with these tools to monitor Tomcat via the JMXProxyServlet. + Plug-in-based monitoring software like Nagios and Icinga may need some help interacting with Tomcat's JMXProxyServlet. [[check_jmx]] is a Perl script that can be used with these tools to monitor Tomcat via the JMXProxyServlet. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Tomcat Wiki] Update of "FAQ/Monitoring" by ChristopherSchultz
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tomcat Wiki" for change notification. The "FAQ/Monitoring" page has been changed by ChristopherSchultz: http://wiki.apache.org/tomcat/FAQ/Monitoring?action=diff&rev1=3&rev2=4 + <> + = Monitoring Tomcat = Monitoring of a running Tomcat instance can be done in several ways, but observing a Tomcat instance via JMX beans will give you the best information available through standard interfaces (i.e. JMX). You can find information about [[http://tomcat.apache.org/tomcat-7.0-doc/monitoring.html|connecting to Tomcat via JMX]] in the Tomcat Users' Guide. Rather than repeating that information here (which is mostly about configuration, connection, etc.), please go read the official documentation. @@ -48, +50 @@ * JMX Bean: `Catalina:type=Manager,context=[context name],host=[hostname]` * Attributes: `activeSessions` + = External Monitoring Tools = + + Plug-in-based monitoring software like Nagios and Icinga may need some help interacting with Tomcat's JMXProxyServlet. [[attachment:check_jmx|check_jmx]] is a Perl script that can be used with these tools to monitor Tomcat via the JMXProxyServlet. + - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Tomcat Wiki] Update of "FAQ/Monitoring" by ChristopherSchultz
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Tomcat Wiki" for change
notification.
The "FAQ/Monitoring" page has been changed by ChristopherSchultz:
http://wiki.apache.org/tomcat/FAQ/Monitoring?action=diff&rev1=2&rev2=3
= Monitoring Tomcat =
- Monitoring of a running Tomcat instance can be done in several ways, but
observing a Tomcat instance via JMX beans will give you the best information
available through standard interfaces (i.e. JMX). You can find information
about [http://tomcat.apache.org/tomcat-7.0-doc/monitoring.html|connecting to
Tomcat via JMX] in the Tomcat Users' Guide. Rather than repeating that
information here (which is mostly about configuration, connection, etc.),
please go read the official documentation.
+ Monitoring of a running Tomcat instance can be done in several ways, but
observing a Tomcat instance via JMX beans will give you the best information
available through standard interfaces (i.e. JMX). You can find information
about [[http://tomcat.apache.org/tomcat-7.0-doc/monitoring.html|connecting to
Tomcat via JMX]] in the Tomcat Users' Guide. Rather than repeating that
information here (which is mostly about configuration, connection, etc.),
please go read the official documentation.
This page is intended to be a community-curated collection of useful JMX
beans that may be useful to you ''after'' you have made your JMX connection and
want to observe interesting data through Tomcat's (and other) JMX beans.
-
- 'NOTE: These JMX bean names are accurate for the current version of
Tomcat 7 (7.0.28 at the time of this writing). If you are using a different
version of Tomcat, you may have to adjust the names of the beans identified on
this page. '
== JVM Information ==
@@ -14, +12 @@
You will certainly want to inspect your JVM's memory usage. Here are some JMX
beans and attributes that can be used to do so.
- JMX Bean: java.lang:type=Memory
+ * JMX Bean: `java.lang:type=Memory`
- Attribute: HeapMemoryUsage
+ * Attribute: `HeapMemoryUsage`
- The attribute value is a javax.management.openmbean.CompositeData which
contains 4 keys: committed, init, max, and used. The 'used' key is probably the
most useful (or a combination of 'used' / 'max' to get a memory-usage metric as
a ratio).
+ The attribute value is a `javax.management.openmbean.CompositeData` which
contains 4 keys: committed, init, max, and used. The 'used' key is probably the
most useful (or a combination of 'used' / 'max' to get a memory-usage metric as
a ratio).
- JMX Bean: java.lang:type=MemoryPool,name=CMS Perm Gen
+ * JMX Bean: `java.lang:type=MemoryPool,name=CMS Perm Gen`
- Attribute: Usage
+ * Attribute: `Usage`
- Similar to the HeapMemoryUsage MXBean described above, this one will give you
information about the "PermGen" heap generation. Depending upon your garbage
collection and other memory settings, you might have different MXBeans under
java.lang:type=MemoryPool with different names. You should inspect each one to
determine if they would be useful for you to inspect.
+ Similar to the `HeapMemoryUsage` MXBean described above, this one will give
you information about the "`PermGen`" heap generation. Depending upon your
garbage collection and other memory settings, you might have different MXBeans
under `java.lang:type=MemoryPool` with different names. You should inspect each
one to determine if they would be useful for you to inspect.
== Tomcat Information ==
+ {{{#!wiki caution
+ Version Warning
+
+ These JMX bean names are accurate for the current version of Tomcat 7 (7.0.28
at the time of this writing). If you are using a different version of Tomcat,
you may have to adjust the names of the beans identified on this page.
+ }}}
+
=== Thread Usage ===
- JMX Bean: Catalina:type=Executor,name=[executor name]
+ * JMX Bean: `Catalina:type=Executor,name=[executor name]`
- Attributes: poolSize, activeCount
+ * Attributes: `poolSize`, `activeCount`
This is the number of threads currently in the executor's thread pool.
Obviously, this is only useful if you are using an (which you
''are'' using, of course, right?).
=== Request Throughput ===
- JMX Bean: Catalina:type=GlobalRequestProcessor,name="[depends]"
+ * JMX Bean: `Catalina:type=GlobalRequestProcessor,name="[depends]"`
- Attributes: bytesSent, bytesReceived, errorCount, maxTime, requestCount
+ * Attributes: `bytesSent`, `bytesReceived`, `errorCount`, `maxTime`,
`requestCount`
- Operations: resetCounters
+ * Operations: `resetCounters`
=== Sessions ===
- JMX Bean: Catalina:type=Manager,context=[context name],host=[hostname]
+ * JMX Bean: `Catalina:type=Manager,context=[context name],host=[hostname]`
- Attributes: activeSessions
+ * Attributes: `activeSessions`
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mai
[Tomcat Wiki] Update of "FAQ/Monitoring" by ChristopherSchultz
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tomcat Wiki" for change notification. The "FAQ/Monitoring" page has been changed by ChristopherSchultz: http://wiki.apache.org/tomcat/FAQ/Monitoring?action=diff&rev1=1&rev2=2 + = Monitoring Tomcat = + Monitoring of a running Tomcat instance can be done in several ways, but observing a Tomcat instance via JMX beans will give you the best information available through standard interfaces (i.e. JMX). You can find information about [http://tomcat.apache.org/tomcat-7.0-doc/monitoring.html|connecting to Tomcat via JMX] in the Tomcat Users' Guide. Rather than repeating that information here (which is mostly about configuration, connection, etc.), please go read the official documentation. This page is intended to be a community-curated collection of useful JMX beans that may be useful to you ''after'' you have made your JMX connection and want to observe interesting data through Tomcat's (and other) JMX beans. + 'NOTE: These JMX bean names are accurate for the current version of Tomcat 7 (7.0.28 at the time of this writing). If you are using a different version of Tomcat, you may have to adjust the names of the beans identified on this page. ' + - == JVM Memory Information == + == JVM Information == + + === Heap and other Memory Information === You will certainly want to inspect your JVM's memory usage. Here are some JMX beans and attributes that can be used to do so. @@ -18, +24 @@ Similar to the HeapMemoryUsage MXBean described above, this one will give you information about the "PermGen" heap generation. Depending upon your garbage collection and other memory settings, you might have different MXBeans under java.lang:type=MemoryPool with different names. You should inspect each one to determine if they would be useful for you to inspect. + == Tomcat Information == + + === Thread Usage === + + JMX Bean: Catalina:type=Executor,name=[executor name] + Attributes: poolSize, activeCount + + This is the number of threads currently in the executor's thread pool. Obviously, this is only useful if you are using an (which you ''are'' using, of course, right?). + + === Request Throughput === + + JMX Bean: Catalina:type=GlobalRequestProcessor,name="[depends]" + Attributes: bytesSent, bytesReceived, errorCount, maxTime, requestCount + Operations: resetCounters + + === Sessions === + + JMX Bean: Catalina:type=Manager,context=[context name],host=[hostname] + Attributes: activeSessions + - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Tomcat Wiki] Update of "FAQ/Monitoring" by ChristopherSchultz
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tomcat Wiki" for change notification. The "FAQ/Monitoring" page has been changed by ChristopherSchultz: http://wiki.apache.org/tomcat/FAQ/Monitoring New page: Monitoring of a running Tomcat instance can be done in several ways, but observing a Tomcat instance via JMX beans will give you the best information available through standard interfaces (i.e. JMX). You can find information about [http://tomcat.apache.org/tomcat-7.0-doc/monitoring.html|connecting to Tomcat via JMX] in the Tomcat Users' Guide. Rather than repeating that information here (which is mostly about configuration, connection, etc.), please go read the official documentation. This page is intended to be a community-curated collection of useful JMX beans that may be useful to you ''after'' you have made your JMX connection and want to observe interesting data through Tomcat's (and other) JMX beans. == JVM Memory Information == You will certainly want to inspect your JVM's memory usage. Here are some JMX beans and attributes that can be used to do so. JMX Bean: java.lang:type=Memory Attribute: HeapMemoryUsage The attribute value is a javax.management.openmbean.CompositeData which contains 4 keys: committed, init, max, and used. The 'used' key is probably the most useful (or a combination of 'used' / 'max' to get a memory-usage metric as a ratio). JMX Bean: java.lang:type=MemoryPool,name=CMS Perm Gen Attribute: Usage Similar to the HeapMemoryUsage MXBean described above, this one will give you information about the "PermGen" heap generation. Depending upon your garbage collection and other memory settings, you might have different MXBeans under java.lang:type=MemoryPool with different names. You should inspect each one to determine if they would be useful for you to inspect. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
