You can now tell whether a slow Java application is short on threads, under memory pressure or just busy. Atatus tracks Apache Tomcat request throughput, processing time and errors alongside thread pool usage, JVM heap and garbage collection. Learn more about Tomcat performance monitoring.
Java developers and operations engineers get server-level metrics next to request-level detail from Atatus APM. That helps them decide whether to tune a thread pool, resize the heap or fix the code.
What you can do
- Request throughput: Track requests per second, bytes sent and received, and error rate for each Tomcat host.
- Processing time: Compare average and maximum request processing time to find the hosts that respond slowly.
- Thread pool usage: See busy and idle threads against the configured maximum to catch thread exhaustion.
- JVM heap and garbage collection: Track heap use against its maximum and how often garbage collection runs.
- Host context: View CPU, memory, load and network traffic for the same host next to the Tomcat metrics.