-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revert "[DBMON-2989] report sql obfuscation error count (#15990)" #16439
Conversation
This reverts commit 5ba30fc.
Codecov Report
Additional details and impacted files
Flags with carried forward coverage won't be shown. Click here to find out more. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, should we drop this metric from metadata.csv
as well, or does it still get reported elsewhere?
If we're dropping it from metadata.csv, I'd argue that this warrants a major version bump as the change becomes essentially breaking for customers that use this metric.
@iliakur this metric |
What does this PR do?
[INCIDENT-24014] This reverts commit 5ba30fc.
Motivation
We've noticed increased memory usage with databases with high cardinality, for example, Postgres with exploded pg_stat_statements, due to this change.
Additional Notes
Review checklist (to be filled by reviewers)
qa/skip-qa
label if the PR doesn't need to be tested during QA.