The Service Map for APM is here!


Agent Check Agent Check

Supported OS: Linux Mac OS Windows

Tomcat Dashboard


This check collects Tomcat metrics like:

  • Overall activity metrics: error count, request count, processing times
  • Thread pool metrics: thread count, number of threads busy
  • Servlet processing times

And more.



The Tomcat check is included in the Datadog Agent package, so you don’t need to install anything else on your Tomcat servers.

This check is JMX-based, so you’ll need to enable JMX Remote on your Tomcat servers. Follow the instructions in the Tomcat documentation to do that.


  1. Edit the tomcat.d/conf.yaml file, in the conf.d/ folder at the root of your Agent’s configuration directory to start collecting your Tomcat metrics and logs. See the sample tomcat.d/conf.yaml for all available configuration options.

  2. Restart the Agent

Metric Collection

  • Add this configuration block to your tomcat.yaml file to start gathering your Tomcat metrics:
    -   host: localhost
        port: 7199
        user: <TOMCAT_USERNAME>
        password: <PASSWORD>
        name: my_tomcat

    - include:
        type: ThreadPool
            alias: tomcat.threads.max
            metric_type: gauge
            alias: tomcat.threads.count
            metric_type: gauge
            alias: tomcat.threads.busy
            metric_type: gauge
    - include:
        type: GlobalRequestProcessor
            alias: tomcat.bytes_sent
            metric_type: counter
            alias: tomcat.bytes_rcvd
            metric_type: counter
            alias: tomcat.error_count
            metric_type: counter
            alias: tomcat.request_count
            metric_type: counter
            alias: tomcat.max_time
            metric_type: gauge
            alias: tomcat.processing_time
            metric_type: counter
    - include:
        j2eeType: Servlet
            alias: tomcat.servlet.processing_time
            metric_type: counter
            alias: tomcat.servlet.error_count
            metric_type: counter
            alias: tomcat.servlet.request_count
            metric_type: counter
    - include:
        type: Cache
          alias: tomcat.cache.access_count
          metric_type: counter
          alias: tomcat.cache.hits_count
          metric_type: counter
    - include:
        type: JspMonitor
          alias: tomcat.jsp.count
          metric_type: counter
          alias: tomcat.jsp.reload_count
          metric_type: counter

See the JMX Check documentation for a list of configuration options usable by all JMX-based checks. The page also describes how the Agent tags JMX metrics.

Restart the Agent to start sending Tomcat metrics to Datadog.

Configuration Options:

  • user and password (Optional) - Username and password.
  • process_name_regex - (Optional) - Instead of specifying a host and port or jmx_url, the agent can connect using the attach api. This requires the JDK to be installed and the path to tools.jar to be set.
  • tools_jar_path - (Optional) - To be set when process_name_regex is set.
  • java_bin_path - (Optional) - Should be set if the agent cannot find your java executable.
  • java_options - (Optional) - Java JVM options
  • trust_store_path and trust_store_password - (Optional) - should be set if “” is set to true on the target JVM.
  • key_store_path and key_store_password - (Optional) - should be set if “” is set to true on the target JVM.
  • rmi_registry_ssl - (Optional) - should be set to true if “” is set to true on the target JVM.

The conf parameter is a list of dictionaries. Only 2 keys are allowed in this dictionary:

  • include (mandatory): Dictionary of filters, any attribute that matches these filters will be collected unless it also matches the “exclude” filters (see below)
  • exclude (optional): Another dictionary of filters. Attributes that match these filters won’t be collected

For a given bean, metrics get tagged in the following manner:


Your metric will be mydomain (or some variation depending on the attribute inside the bean) and have the tags attr0:val0, attr1:val1, domain:mydomain.

If you specify an alias in an include key that is formatted as camel case, it will be converted to snake case. For example, MyMetricName will be shown in Datadog as my_metric_name.

See the sample tomcat.yaml for all available configuration options.

The attribute filter

The attribute filter can accept two types of values:

  • A dictionary whose keys are attributes names:

    conf: - include: attribute: maxThreads: alias: tomcat.threads.max metric_type: gauge currentThreadCount: alias: tomcat.threads.count metric_type: gauge bytesReceived: alias: tomcat.bytes_rcvd metric_type: counter

In that case you can specify an alias for the metric that will become the metric name in Datadog. You can also specify the metric type either a gauge or a counter. If you choose counter, a rate per second will be computed for this metric.

  • A list of attributes names:

    conf: - include: domain: org.apache.cassandra.db attribute: - BloomFilterDiskSpaceUsed - BloomFilterFalsePositives - BloomFilterFalseRatio - Capacity - CompressionRatio - CompletedTasks - ExceptionCount - Hits - RecentHitRate

In that case:

  • The metric type is a gauge
  • The metric name is jmx.\[DOMAIN_NAME].\[ATTRIBUTE_NAME]

Here is another filtering example:

  - host:
    name: jmx_instance
    port: 9999

    - include:
        bean: org.apache.cassandra.metrics:type=ClientRequest,scope=Write,name=Latency
          - OneMinuteRate
          - 75thPercentile
          - 95thPercentile
          - 99thPercentile


List of filters is only supported in Datadog Agent > 5.3.0. If you are using an older version, please use singletons and multiple include statements instead.

# Datadog Agent > 5.3.0
    - include:
        domain: domain_name
          - first_bean_name
          - second_bean_name

# Older Datadog Agent versions
    - include:
        domain: domain_name
        bean: first_bean_name
    - include:
        domain: domain_name
        bean: second_bean_name

Log Collection

Available for Agent >6.0

Tomcat uses by default the log4j logger. To activate the logging into a file and customize the log format edit the file in the $CATALINA_BASE/lib directory as follows:

log4j.rootLogger = INFO, CATALINA

 # Define all the appenders
log4j.appender.CATALINA = org.apache.log4j.DailyRollingFileAppender
log4j.appender.CATALINA.File = /var/log/tomcat/catalina.log
log4j.appender.CATALINA.Append = true

 # Roll-over the log once per day
log4j.appender.CATALINA.layout = org.apache.log4j.PatternLayout
log4j.appender.CATALINA.layout.ConversionPattern = %d{yyyy-MM-dd HH:mm:ss} %-5p [%t] %c{1}:%L - %m%n

log4j.appender.LOCALHOST = org.apache.log4j.DailyRollingFileAppender
log4j.appender.LOCALHOST.File = /var/log/tomcat/localhost.log
log4j.appender.LOCALHOST.Append = true
log4j.appender.LOCALHOST.layout = org.apache.log4j.PatternLayout
log4j.appender.LOCALHOST.layout.ConversionPattern = %d{yyyy-MM-dd HH:mm:ss} %-5p [%t] %c{1}:%L - %m%n

log4j.appender.MANAGER = org.apache.log4j.DailyRollingFileAppender
log4j.appender.MANAGER.File = /var/log/tomcat/manager.log
log4j.appender.MANAGER.Append = true
log4j.appender.MANAGER.layout = org.apache.log4j.PatternLayout
log4j.appender.MANAGER.layout.ConversionPattern = %d{yyyy-MM-dd HH:mm:ss} %-5p [%t] %c{1}:%L - %m%n

log4j.appender.HOST-MANAGER = org.apache.log4j.DailyRollingFileAppender
log4j.appender.HOST-MANAGER.File = /var/log/tomcat/host-manager.log
log4j.appender.HOST-MANAGER.Append = true
log4j.appender.HOST-MANAGER.layout = org.apache.log4j.PatternLayout
log4j.appender.HOST-MANAGER.layout.ConversionPattern = %d{yyyy-MM-dd HH:mm:ss} %-5p [%t] %c{1}:%L - %m%n

log4j.appender.CONSOLE = org.apache.log4j.ConsoleAppender
log4j.appender.CONSOLE.layout = org.apache.log4j.PatternLayout
log4j.appender.CONSOLE.layout.ConversionPattern = %d{yyyy-MM-dd HH:mm:ss} %-5p [%t] %c{1}:%L - %m%n

 # Configure which loggers log to which appenders[Catalina].[localhost] = INFO, LOCALHOST[Catalina].[localhost].[/manager] =\
  INFO, MANAGER[Catalina].[localhost].[/host-manager] =\

Check Tomcat logging documentation for more information about Tomcat logging capabilities.

By default, our integration pipeline support the following conversion patterns:

  %d{yyyy-MM-dd HH:mm:ss} %-5p %c{1}:%L - %m%n
  %d [%t] %-5p %c - %m%n

Make sure you clone and edit the integration pipeline if you have a different format.

  • Collecting logs is disabled by default in the Datadog Agent, enable it in your datadog.yaml file with:
  logs_enabled: true
  • Add this configuration block to your tomcat.d/conf.yaml file to start collecting your Tomcat Logs:
    - type: file
      path: /var/log/tomcat/*.log
      source: tomcat
      service: myapp
      #To handle multi line that starts with yyyy-mm-dd use the following pattern
      #  - type: multi_line
      #    name: log_start_with_date
      #    pattern: \d{4}\-(0?[1-9]|1[012])\-(0?[1-9]|[12][0-9]|3[01])

Change the path and service parameter values and configure them for your environment. see the sample tomcat.yaml for all available configuration options.


Run the Agent’s status subcommand and look for tomcat under the Checks section.

Data Collected


The maximum number of allowed worker threads.
shown as thread
The number of threads managed by the thread pool.
shown as thread
The number of threads that are in use.
shown as thread
Bytes per second sent by all the request processors.
shown as byte
Bytes per second received by all request processors.
shown as byte
The number of errors per second on all request processors.
shown as error
The number of requests per second across all request processors.
shown as request
The longest request processing time (in milliseconds).
shown as millisecond
The sum of request processing times across all requests handled by the request processors (in milliseconds) per second.
The sum of request processing times across all requests to the servlet (in milliseconds) per second.
The number of erroneous requests received by the servlet per second.
shown as error
The number of requests received by the servlet per second.
shown as request
The number of accesses to the cache per second.
shown as get
The number of cache hits per second.
shown as hit
The number of JSPs per second that have been loaded in the web module.
shown as page
The number of JSPs per second that have been reloaded in the web module.
shown as page


The Tomcat check does not include any events at this time.

Service Checks


Returns CRITICAL if the Agent is unable to connect to and collect metrics from the monitored Tomcat instance. Returns OK otherwise.


Commands to view the metrics that are available:

The datadog-agent jmx command was added in version 4.1.0.

  • List attributes that match at least one of your instances configuration: sudo /etc/init.d/datadog-agent jmx list_matching_attributes
  • List attributes that do match one of your instances configuration but that are not being collected because it would exceed the number of metrics that can be collected: sudo /etc/init.d/datadog-agent jmx list_limited_attributes
  • List attributes that will actually be collected by your current instances configuration: sudo /etc/init.d/datadog-agent jmx list_collected_attributes
  • List attributes that don’t match any of your instances configuration: sudo /etc/init.d/datadog-agent jmx list_not_matching_attributes
  • List every attributes available that has a type supported by JMXFetch: sudo /etc/init.d/datadog-agent jmx list_everything
  • Start the collection of metrics based on your current configuration and display them in the console: sudo /etc/init.d/datadog-agent jmx collect

Further Reading

Mistake in the docs? Feel free to contribute!