Eclipse Jetty extension
- Latest Dynatrace
- Extension
- Published Oct 27, 2025
Monitor and analyze Jetty applications with automated, intelligent observability.
Monitor Jetty applications with deep code insights, automatic tracing, and performance metrics.
Get started
Overview
With Dynatrace, you can get observability for all applications and microservices deployed in your Jetty web server, including automatic end-to-end tracing, metrics and log insights. Dynatrace deep code level insights will give you CPU profiling insights including method hotspots, insights into calls to databases, error/exception analysis, and much more. Comprehensive out-of-the-box metrics will give you insights into memory allocation, garbage collection, and thread behavior.
The Jetty JMX server monitoring extension in Dynatrace provides information about your Jetty application, including insights into connections, requests and threads. These metrics will help you find and understand the root cause of any issues or problems with your Jetty application.
This is a JMX (Java Management Extension) Dynatrace extension. JMX is ideal for monitoring applications built using Java. Make sure you are monitoring your Jetty process.
Use cases
-
Baseline and detect problems automatically for apps, user actions, and requests.
-
Identify intelligent, actionable root causes of service problems.
-
Understand how remote services like databases and queues impact performance.
-
View logs in the context of traces and workloads.
-
Profile CPU and memory continuously with production-grade, always-on monitoring.
-
Troubleshoot issues with deep code-level visibility down to a single line.
Requirements
If your Jetty runs on a virtual machine or bare-metal, install OneAgent to get started.
If your Jetty runs as a workload in Kubernetes or OpenShift, set up Dynatrace on Kubernetes or OpenShift.
Activate the OneAgent features to get tracing insight:
- Java Servlet 5.0
Activate the Jetty JMX extension to get metric insight by selecting Add to environment and setting up a configuration.
Activate log monitoring to get log insight.
- Jetty application with the OneAgent installed on version 1.273+
- Windows or Linux
Compatibility information
-
Metric support by Jetty version:
-
Version 12:
- Does not support
errorsandresponsesBytesTotal
- Does not support
-
Version < 12:
- Does not support
failures,bytesRead,bytesWrittenandhandleTime
- Does not support
Details
The dashboard Jetty JMX Overview will be included in the extension, where you can see an overview of your Jetty JMX metrics.
Additionally, all metrics captured by the extension will be appended to the process group instance's unified analysis screen in three new sections: threads, time usage and traffic. Make sure to be on the new screen for process group instances to see them by clicking on Metrics and logs analysis on the process view.
All metrics can also be viewed with the data explorer.
Licensing and cost
The extension consumes DDUs. However, they are eligible for the free tier included with every host. The amount of DDUs depends on the number of instances monitored.
Feature sets
When activating your extension using monitoring configuration, you can limit monitoring to one of the feature sets. To work properly the extension has to collect at least one metric after the activation.
In highly segmented networks, feature sets can reflect the segments of your environment. Then, when you create a monitoring configuration, you can select a feature set and a corresponding ActiveGate group that can connect to this particular segment.
All metrics that aren't categorized into any feature set are considered to be the default and are always reported.
A metric inherits the feature set of a subgroup, which in turn inherits the feature set of a group. Also, the feature set defined on the metric level overrides the feature set defined on the subgroup level, which in turn overrides the feature set defined on the group level.
Connections
| Metric name | Metric key | Description |
|---|---|---|
| Jetty new connections | jetty.connections.count | — |
| Jetty open connections | jetty.connectionsOpen | — |
Response codes
| Metric name | Metric key | Description |
|---|---|---|
| Jetty 1xx responses | jetty.response1xx.count | — |
| Jetty 2xx responses | jetty.response2xx.count | — |
| Jetty 3xx responses | jetty.response3xx.count | — |
| Jetty 4xx responses | jetty.response4xx.count | — |
| Jetty 5xx responses | jetty.response5xx.count | — |
Threads basic metrics
| Metric name | Metric key | Description |
|---|---|---|
| Jetty busy threads | jetty.busyThreads | — |
| Jetty idle threads | jetty.idleThreads | — |
Messages
| Metric name | Metric key | Description |
|---|---|---|
| Jetty messages in | jetty.messagesIn.count | — |
| Jetty messages out | jetty.messagesOut.count | — |
Traffic
| Metric name | Metric key | Description |
|---|---|---|
| Jetty total response bytes | jetty.responsesBytesTotal.count | — |
| Jetty bytes read | jetty.bytesRead | — |
| Jetty bytes written | jetty.bytesWritten | — |
Time usage
| Metric name | Metric key | Description |
|---|---|---|
| Jetty total request time | jetty.requestTime.count | — |
| Jetty total handle time | jetty.handleTime.count | — |
Threads extra metrics
| Metric name | Metric key | Description |
|---|---|---|
| Jetty leased threads | jetty.leasedThreads | — |
| Jetty ready threads | jetty.readyThreads | — |
| Jetty reserved threads | jetty.reservedThreads | — |
Requests
| Metric name | Metric key | Description |
|---|---|---|
| Jetty request queue size | jetty.queueSize | — |
| Jetty request count | jetty.requestCount.count | — |
| Jetty request failures | jetty.failures.count | — |
| Jetty request errors | jetty.errors.count | — |
| Jetty active request count | jetty.requestsActive.count | — |
