Connection Pools WebLogic extension cost calculation

[andre_vdveen]

Hi, the Connection Pools WebLogic extension doesn't list a formula to calculate cost usage like most extensions do - does anyone know what the formula would be, or could the extension creater perhaps supply it on the documentation and/or Hub page? @Mike_L 

[Mike_L]

Thanks for the feedback, I'll ask the extension creator to create it.

[victor_balbuena]

The formula for the amount of datapoints per minute would be the following:

(22 * # of WebLogic Connection Pool/Server Runtime)

+ (1 * # of WebLogic Connection Pools/Config Paths)

+ (3 * # of WebLogic Connection Pools/Server Runtime/JMS Server Runtime)

+ (2 * # of Server runtimes)

We're in the process of adding it to the docs for clarity right now.

Do consider, however, that as with any OneAgent extension, the metric datapoints from this extension consume first the included DDUs per host unit as indicated in this doc page: https://docs.dynatrace.com/docs/license/monitoring-consumption-classic/davis-data-units/metric-cost-...

[andre_vdveen]

Perhaps a silly question but is there a way to see how many connection pools there are, directly in Dynatrace, without enabling the extension, instead of having to rely on the admininstrators to retrieve the info that's required for the calculation?
In large organisations, it is very difficult to obtain the necessary info for the calculation and if the incorrect info is provided, the cost could be very different than what is calculated. Some clients don't want to enable extensions for e.g., 24 hours to get a ballpark cost due to concerns of what the cost could potentially (example: F5 and VMware extensions are quite heavy on cost).