cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

This product reached the end of support date on March 31, 2021.

JDBC sensor configuration and performance

jcamps
DynaMight Advisor
DynaMight Advisor

Hi all,

what's the impact of enabling de bind value capturing and increase the Maximum SQL Command capture length of the JDBC sensor in a Production System? Affects the monitored application performance or only the Dynatrace Server?

Regards, Josep Maria

6 REPLIES 6

Babar_Qayyum
DynaMight Leader
DynaMight Leader

Hello Josep,

As per below statement the overhead is high and that will be on the SUD.

Toggle bind value capturing off (much overhead; off by default).

Regards,

Babar

Hi Babar,

ok, but you know how much overhead? My customer wants to know that to decide...

Regards, Josep Maria

Zach_Jacobs
Participant

Hello,

Enabling bind value capturing will incur some overhead on the monitoring application as reflection calls are made to retrieve SQLString and bind parameters in the trace tag. See the below link to the JDBC Sensor documentation.

https://community.dynatrace.com/community/display/DOCDT65/JDBC+Sensor

Hi Zach,

thanks for your response!

Regards,

Josep Maria

peter_karlhuber
Dynatrace Pro
Dynatrace Pro

The noticeable overhead is memory consumption in the agent, i.e. inside the monitored application. This is valid for all sensor configurations regarding string lengths, like exception stack traces, SQL length, bind values etc.

Hi Peter,

thanks for your response!

Regards,

Josep Maria