Apache Tomcat is an open source servlet container and web server from the Apache Software Foundation. It implements several Java EE specifications including Java Servlet, JavaServer Pages (JSP), Java Expression Language (EL) and WebSocket and provides a “pure Java” HTTP web server environment for Java code to run in. Tomcat is used to deploy and serve web applications.
The prerequisites for monitoring Tomcat with Netdata are to have Tomcat and Netdata installed on your system.
Netdata auto discovers hundreds of services, and for those it doesn’t turning on manual discovery is a one line configuration. For more information on configuring Netdata for Tomcat monitoring please read the collector documentation.
You should now see the Tomcat section on the Overview tab in Netdata Cloud already populated with charts about all the metrics you care about.
Netdata has a public demo space (no login required) where you can explore different monitoring use-cases and get a feel for Netdata.
Requests per second is a metric that measures the number of requests made to a Tomcat server in a given second. This metric is important to monitor to ensure that the server is not overloaded with requests and can handle its workload. If the requests per second is too high, the server may experience performance issues or even become unresponsive.
Volume is a metric that measures the amount of data that is being transferred between the Tomcat server and the network. This metric is important to monitor in order to ensure that the server is not overloaded with data, which can lead to decreased performance or even a crash. Normal values for volume range from 0 to 500 MB per second, depending on the size and activity of the server.
Threads are a metric that measures the number of threads that are currently running on the Tomcat server. This metric is important to monitor in order to ensure that the server has enough resources to handle its workload. If the number of threads is too low, the server may experience performance issues or even become unresponsive. The number of current threads should be monitored, as well as the number of busy threads, which is the number of threads that are actively processing requests.
JVM Free Memory is a metric that measures the amount of free memory available in the Java Virtual Machine. This metric is important to monitor in order to ensure that the server has enough resources to handle its workload. If the amount of free memory is too low, the server may experience performance issues or even become unresponsive.