Connection Pools WebLogic extension
- Latest Dynatrace
- Extension
Collect the connection pool performance, usage and availability metrics for Oracle Weblogic.
Connection Pools allow you to monitor connection pool performance and identify issues such as connection leaks.
Get started
Overview
Several built-in OneAgent extensions provide an insight into the connection pool performance and issues such as connection leaks. The extensions cover the following technologies: Apache Tomcat, Oracle WebLogic, IBM WebSphere Application Server, IBM WebSphere Liberty, Red Hat JBoss and Apache Commons.
Use cases
- Collect the connection pool performance, usage and availability metrics for Oracle Weblogic.
Compatibility information
- Oracle Weblogic process that runs on a supported Linux or Windows operating system.
- OneAgent version 1.273+
- Dynatrace version 1.273+
Activation and setup
- Install OneAgent on the virtual machine or server of your Oracle Weblogic process.
- Activate the OneAgent feature
Java Metric Extensions 2.0 (JMX). - Select Add to environment in the same tile to configure the extension.
- Open the Weblogic Connection Pool Overview dashboard.
Details
Licensing and costs
There is no charge to use the extension. You are only charged for the data that the extension ingests.
The Connection Pools WebLogic extension ingests custom metrics, which consume Davis Data Units (DDUs) (Dynatrace classic license) or Metrics powered by Grail (DPS), according to your license model.
License consumption is based on the number of connection pools and server runtimes. The following formula provides approximate metric data points ingested per minute with all feature sets enabled. Note that this is only an approximation as the true numbers will depend heavily on the traffic you experience.
(22 * # of WebLogic Connection Pools and Server Runtimes) + (1 * # of WebLogic Connection Pools and Config Paths) + (3 * # of WebLogic Connection Pools, Server Runtimes, and JMS Server Runtimes) + (2 * # of Server runtimes)
Dynatrace Platform Subscription
In the Dynatrace Platform Subscription, metric ingestion consumes Metrics powered by Grail according to the number of ingested metric data points.
To calculate the approximate yearly consumption, apply the following calculation: <metric data points per minute> * 60 minutes * 24 hours * 365 days.
Dynatrace classic license
In the classic licensing model, metric ingestion consumes Davis Data Units (DDUs) at the rate of .001 DDUs per metric data point. Multiply the above formula for annual data points by .001 to estimate annual DDU usage.
The DDU cost above does not include any possible log events or custom events that are triggered by the extension. For more information, see DDU events.
Feature sets
When activating your extension using a 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.
cache
| Metric name | Metric key | Description |
|---|---|---|
| Statement cache size | weblogic.connectionPool.prepStmtCacheCurrentSize | — |
| Statement cache hits | weblogic.connectionPool.prepStmtCacheHitCount.count | — |
| Statement cache misses | weblogic.connectionPool.prepStmtCacheMissCount.count | — |
capacity
| Metric name | Metric key | Description |
|---|---|---|
| Max capacity | weblogic.connectionPool.maxCapacity | — |
Messaging
| Metric name | Metric key | Description |
|---|---|---|
| Current message count | weblogic.currentMessages | — |
| Pending message count | weblogic.pendingMessages | — |
| Total message count | weblogic.totalMessages | — |
connections
| Metric name | Metric key | Description |
|---|---|---|
| Active connections | weblogic.connectionPool.activeConnectionsCurrentCount | — |
| Current capacity | weblogic.connectionPool.currCapacity | — |
| Leaked connections | weblogic.connectionPool.leakedConnectionCount.count | — |
| Available connections (idle) | weblogic.connectionPool.numAvailable | — |
| Waiting for connections | weblogic.connectionPool.waitingForConnectionCurrentCount | — |
| Failed connection requests | weblogic.connectionPool.failedReserveRequestCount.count | — |
| Reconnection failures | weblogic.connectionPool.failuresToReconnectCount.count | — |
| Requests for connections | weblogic.connectionPool.reserveRequestCount.count | — |
Threading
| Metric name | Metric key | Description |
|---|---|---|
| Stuck thread count | weblogic.stuckThreads | — |
| Hogging thread count | weblogic.hoggingThreads | — |
