[DBMON-3271] DBM integrations now defaulted to use new go-sqllexer pkg to obfuscate sql statements #16681
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This PR defaults postgres, mysql and sqlserver integrations'
obfuscation_mode
toobfuscate_and_normalize
. With this change, the integration will usego-sqllexer
as the default sql statements obfuscator.Motivation
Default to
go-sqllexer
as the default sql statements obfuscator to better obfuscation on edge cases and error handling.Additional Notes
Review checklist (to be filled by reviewers)
qa/skip-qa
label if the PR doesn't need to be tested during QA.