IBM WebSphere Liberty extension
- Latest Dynatrace
- Extension
- Published Oct 27, 2025
Monitor IBM WebSphere Liberty to gain deep visibility into app performance and service health.
Get started
Overview
Dynatrace automatically detects all applications and microservices deployed in your application server and provides automatic end-to-end tracing, application server metrics and log insights. Dynatrace visualizes your web application and its dependencies from website to application to container, infrastructure and cloud. It diagnoses anomalies in real-time with AI and pinpoints the root-cause down to the broken code before your customers are even affected. Deep code-level insights combined with market-leading profiling capabilities like method hotspots, error/exception analysis, memory profiling, and thread analysis will help you leverage the robustness of your production environment.
Use cases
- Capture every transaction, across every tier, without gaps or blind spots.
- Understand all dependencies of your applications including all database statements executed and their performance.
- Improve the performance of your Java code with continuous insights into your applications.
- Profile CPU, memory and thread problems with Dynatrace' industry leading production grade continous profiler.
- Detect availability and performance problems across your stack proactively.
- Monitor all your application metrics via Dynatrace's builtin JMX monitoring capability.
- Leverage open observability frameworks like OpenTelemetry or Micrometer to add custom metrics and custom traces instrumentation.
Requirements
- Windows or Linux
- OneAgent version 1.275+
- Dynatrace version 1.309+
- Java Metric Extensions 2.0 (JMX) [Opt-In] OneAgent feature enabled.
If your WebSphere Liberty is running on a virtual machine directly, install OneAgent on that virtual machine to get started.
If your WebSphere Liberty is running as a workload in Kubernetes, set up Dynatrace on Kubernetes.
If your WebSphere Liberty is running as a workload in OpenShift, set up Dynatrace on OpenShift.
Activate the JMX extensions for WebSphere Liberty appserver and WebSphere Liberty connection pools to get full metric insight by selecting Add to environment.
Activate the built-in detection rule to automatically detect the WebSphere Liberty server name.
Activate log monitoring to get full log insight.
Details
The dashboard WebSphere Liberty JMX Overview will be included in the extension, where you can see an overview of your WebSphere Liberty 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: JVM, Servlet and Thread pools. Make sure to be on the new screen for process group instances to see them.
All metrics can also be viewed with the data explorer.
Licensing and cost
The extension consumes DDUs. However, the free tier included with every host applies. You can further control this consumption by turning metrics on and off via the use of feature sets. The amount of DDUs consumed 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.
Request timing
| Metric name | Metric key | Description |
|---|---|---|
| Active requests | websphere.liberty.ActiveRequestCount | Number of active requests |
| Slow requests | websphere.liberty.SlowRequestCount | Number of slow requests |
| Hung requests | websphere.liberty.HungRequestCount | Number of hung requests |
Servlet
| Metric name | Metric key | Description |
|---|---|---|
| Request count | websphere.liberty.RequestCount.count | Request count |
| Response time | websphere.liberty.ResponseTime | Response time |
JVM
| Metric name | Metric key | Description |
|---|---|---|
| JVM Heap size | websphere.liberty.jvm.Heap | Total heap size for websphere liberty |
| JVM Heap available | websphere.liberty.jvm.FreeMemory | Free heap available for websphere liberty |
| JVM Heap used | websphere.liberty.jvm.UsedMemory | Used heap for websphere liberty |
| JVM CPU usage | websphere.liberty.jvm.ProcessCPU | Percentage of CPU consumed by this JVM |
| JVM Garbage collection | websphere.liberty.jvm.GcCount.count | Number of times that GC happened |
| JVM Garbage collection time | websphere.liberty.jvm.GcTime.count | Amount of time spent on garbage collection |
| JVM uptime | websphere.liberty.jvm.UpTime | Time since the JVM started |
Thread pool
| Metric name | Metric key | Description |
|---|---|---|
| Active threads | websphere.liberty.ActiveThreads | Active threads |
| Pool size | websphere.liberty.PoolSize | Pool size |
