APM Insight provides information on the parameters it sends to the SQL queries
The parameters in slow SQL queries can be tracked and displayed under the traces tab.
We have the option to obfuscate the values of SQL query parameters using a configuration "Obfuscate SQL Parameters". It will be enabled by default. The screenshot below shows the configuration for parameterizing the SQL queries.
Please find the below screenshots for inline SQL queries:
When the option is enabled, the parameter values will be obfuscated as given below:
> SQL inline query with obfuscated parameter values
When the option is disabled, the parameter values will not be obfuscated as given below:
> SQL inline query without obfuscating the parameter values
New to ADSelfService Plus?
Related Articles
APM Insight Troubleshooting - FAQs
Monitor Addition - FAQs 1. How to add an APM Insight Monitor? After you deploy the APM Insight agent in your Application Server with suitable Applications Manager credentials in the apminsight.conf file, APM Insight monitors will automatically be ...Uninstrumented Block of Code - APM Insight
In the traces tab --> Slowest Method Calls and Count we show if you find Un-instrumented block of code the reason is as follows: Basically, What is un-instrumented block of code in APM Insight? By default, APM Insight agent monitors known frameworks ...Self monitor Applications Manager using APM Insight Java Agent
Applications Manager is built with Java, hence we can monitor it using APM Insight Java Agent to measure it's performance continuously, which can be very much useful. Setting up APM Insight Java Agent Follow the below steps to download and set up the ...How to rename an existing APM - Java agent application's monitor?
In Applications Manager's APM(Application Performance Monitoring) doesn't support renaming applications/monitors from the web client. However, the application name of an existing application instance can be renamed in the `apminsight.conf` file and ...Troubleshooting Applications Manager Plugin database migration failure after service pack upgrade of OPM and APM plugin
When upgrading OpManager from version 12.6.xxx to 12.7.xxx and updating the APM Plugin to 1651x, particularly when using Postgresql as the backend database, an essential one-time migration occurs. This migration involves moving our backend Postgresql ...