Open Q&A
If there's no good subforum for your question - ask it here!
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Turn off capturing of DB Prepare statements

gilgi
DynaMight Champion
DynaMight Champion

Hi, 

While Database prepare statements may be beneficial, I've seen more than once situations in which the DB prepare statements (in an intensive database based application) take a huge percentage of the allowed trace ingest quota for the V3 platform. This results in a customers missing out crucial spans and having to pay for additional storage because of spans they do not want.
My question to you: did you face such situations? how did you handle that? and for the Dynatrace guys our here - do you know of any way to just turn off the prepare statements collection?

Gil.

2 REPLIES 2

AravindhanV
Advisor

Hi @gilgi ,

Its Valid question, how about using the Bind Variables,

Understanding would be, Bind variables allow the database server to prepare the statement once and execute it multiple times without reparsing or reanalyzing it.

Settings > Server-side service monitoring > Deep monitoring

Under Database Capture SQL bind values.

Have a look and share your thought

Thanks

aravind

dylan_taelemans
Advisor

If you're using Dynatrace SaaS, you could try using OpenPipeline to drop them.

Something similar to this:

dylan_taelemans_0-1784273212551.png

 

Featured Posts