SQL bind values filled with asterix " * "
Dennis, do you have a screenshot of this?
Ahmed
Hi Ahmed,
No, I dont unfortunately. Restricted customer access.
Best regards,
Dennis
I assume you already enabled capturing bind values in the sensor configuration. Did you also check if the privacy settings are masking the bind values? Settings > dynaTrace Server > Settings > Confidential Strings
Ahmed
Hi Ahmed,
Thanks, I checked the server settings. It was activated there. However, strange that I see it for some and for some not. Also, the description for these server settings say, that it is for setting confidential strings when "exporting a session". However, I was looking at live data.
Best regards,
Dennis
Dennis, which Dyntrace AM version is used there? I think that the Confidential String setting also applies to live data as per the Hint: "This will apply to live / stored sessions and to dashboards where the user does not have permissions to see the values."
It is indeed strange that you see the bind values for some statements and do not see them for others. Is there any difference in DB platform or character encoding that might cause this?
Is it that you either see asterisks or "preparation"? We put "preparation" to differentiate between executed and prepared statements, this wouldn't be censored out as with other confidential strings if your user doesn't have the permission "Read Confidential Strings"
Rick B
Hi,
Any idea why for the most SQL statements I see bind values but for some I have only " * " (asterix)? While I can imagine that for some bind values this might be ok due to the fact that it is binary data, I dont understand that for others... any idea? (since I see a lot of bind values already, I can assume configuration is correct?!)
Best regards,
Dennis