Documentation forServer & Application Monitor
Monitoring your applications and environment is a key capability of Hybrid Cloud Observability and is also available in a standalone module, Server & Application Monitor (SAM). Hybrid Cloud Observability and SAM are built on the self-hosted SolarWinds Platform.

Tomcat Server

Use the SAM application monitor template to collect statistics for Apache Tomcat servers that run on JVMs in your environment.

This template includes Tomcat Server Monitors, such as Tomcat Free Memory, that you can use to check for Certificate Authority (CA), Common Name (CA), or Certificate Revocation List (CRL) errors on target systems.

Server configuration

Configure Java application servers and JVMs for SAM monitoring.

If you experience issues with Tomcat Server monitors on AIX systems, enable remote access in the following Tomcat configuration file: conf/Catalina/localhost/manager.xml

To use the SolarWinds Platform agent for Linux instead of agentless SNMP polling, see Configure Linux/Unix systems for monitoring by the SolarWinds Platform agent in SAM.


Provide Tomcat credentials for a user associated with the Manager role, as configured in the tomcat-users.xml file on target JVMs. Here is an example:

<role rolename="manager"/> <user username="user" password="pass" roles="manager"/>

Component monitors

Note the following details about component monitors included in this template:

  • (Recommended) After initial setup, monitor counters for a few weeks to understand potential value ranges within your environment, and then set the thresholds accordingly. See Understand application monitor thresholds.
  • By default, all components use port 8080. If target systems use another port, update the Port Number used by all components.

Tomcat Free Memory

The amount of heap space currently available to the JVM. This value should be as high as possible. The heap space may be of a fixed size or may be expanded and shrunk, depending on the garbage collector's strategy.

Tomcat Total Memory

The total amount of memory currently allocated to the JVM heap space. This value should be as low as possible. You should set thresholds according to your Tomcat Max Memory value. If the returned value is near the Tomcat Max Memory value or you received OutOfMemoryError errors, you may need to increase the heap size.

Tomcat Max Memory

The maximum size of the heap space, not including the permanent generation area.

Tomcat Total Processing Time

The total processing time, in milliseconds, since the server started.

Tomcat Total Request Count

The total number of requests from the server since the server started.

Tomcat Total Bytes Sent

The total number of bytes sent from the server since the server started.

Tomcat Total Bytes Received

The total number of bytes sent to the server since the server started.

Tomcat Total Errors Count

The total number of errors from all request processors.