-
Notifications
You must be signed in to change notification settings - Fork 1.5k
SDBM-2260 Make query error tracking optional, default true #22259
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
base: master
Are you sure you want to change the base?
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files🚀 New features to boost your workflow:
|
f1f05de to
5091666
Compare
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.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
5091666 to
fa30427
Compare

What does this PR do?
In SDBM-2260 we have a user who upgraded to Agent 7.73 and started seeing issues with performance related to the Query Errors query starting with
SUM(SUM_ERROR_RAISED), causing them to downgrade the agent. The query runtime ranges from 18s - 50s on their host. The query was introduced in this PR.There are no performance issues with this query in our integration environments, and on most of the hosts in that user's environment, so part of the investigation will be understanding why that particular host is seeing high runtimes. The current theory is that there is some contention on
performance_schemathat might be caused by RDS Performance Insights making queries to the same table. In the meantime this PR makes the query configurable, but default true, for users that are having issues with it.Motivation
Review checklist (to be filled by reviewers)
qa/skip-qalabel if the PR doesn't need to be tested during QA.backport/<branch-name>label to the PR and it will automatically open a backport PR once this one is merged