Eclipse JettyEclipse Jetty
Automatically and intelligently monitor and analyze your Jetty applications.
Extension
- Product information
- Release notes
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.
Use cases
- Automatic baselining and problem detection for your apps and their user actions and requests.
- Intelligent and actionable root cause detection in case of service problems.
- Understand the impact of remote services such as databases and queues.
- See logs in context of your traces and workloads.
- Always-on, 24/7, production-grade CPU and memory profiling
- Deep code-level visibility to troubleshoot issues down to a single line of code.
Get started
If your Jetty runs on a virtual machine or bare-metal, install OneAgent on it 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 clicking on Add to environment and setting up a configuration.
Activate log monitoring to get log insight.
Extension
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.
Click on Add to environment to get started.
Prerequisites
- Jetty application with the OneAgent installed on version 1.273+
- Windows or Linux
Output
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 Consumption
The extension consumes DDUs. However, they are elgible for the free tier included with every host. The amount of DDUs depends on the number of instances monitored.
Extension content
Feature sets
Below is a complete list of the feature sets provided in this version. To ensure a good fit for your needs, individual feature sets can be activated and deactivated by your administrator during configuration.
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Jetty leased threads | jetty.leasedThreads | - | Count |
| Jetty ready threads | jetty.readyThreads | - | Count |
| Jetty reserved threads | jetty.reservedThreads | - | Count |
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Jetty total response bytes | jetty.responsesBytesTotal.count | - | Byte |
| Jetty bytes read | jetty.bytesRead | - | Bytes |
| Jetty bytes written | jetty.bytesWritten | - | Bytes |
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Jetty messages in | jetty.messagesIn.count | - | Count |
| Jetty messages out | jetty.messagesOut.count | - | Count |
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Jetty busy threads | jetty.busyThreads | - | Count |
| Jetty idle threads | jetty.idleThreads | - | Count |
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Jetty 1xx responses | jetty.response1xx.count | - | Count |
| Jetty 2xx responses | jetty.response2xx.count | - | Count |
| Jetty 3xx responses | jetty.response3xx.count | - | Count |
| Jetty 4xx responses | jetty.response4xx.count | - | Count |
| Jetty 5xx responses | jetty.response5xx.count | - | Count |
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Jetty new connections | jetty.connections.count | - | Count |
| Jetty open connections | jetty.connectionsOpen | - | Count |
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Jetty request queue size | jetty.queueSize | - | Count |
| Jetty request count | jetty.requestCount.count | - | Count |
| Jetty request failures | jetty.failures.count | - | Count |
| Jetty request errors | jetty.errors.count | - | Count |
| Jetty active request count | jetty.requestsActive.count | - | Count |
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Jetty total request time | jetty.requestTime.count | - | Second |
| Jetty total handle time | jetty.handleTime.count | - | Second |
Full version history
Full version history
- Conversion from EF1.0 to EF2.0 with JMX data source
- Added graphs injected into the unified analysis screens of both the process and the host
- Added extension overview dashboard
- Added feature sets to control which metrics to ingest
- Added new metrics:
- jetty.readyThreads
- jetty.reservedThreads
- func:jetty.totalThreads
- jetty.requestsActive.count
- jetty.failures.count
- jetty.errors.count
- jetty.messagesIn.count
- jetty.messagesOut.count
- jetty.requestTime.count
- jetty.handleTime.count
- jetty.bytesRead
- jetty.bytesWritten
- jetty.response1xx.count
- jetty.response2xx.count
- jetty.response3xx.count
- jetty.response4xx.count
- jetty.response5xx.count
