-
-
Notifications
You must be signed in to change notification settings - Fork 63
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
Long Running Queries Excepitons #1061
Comments
What criteria would you like to use to exclude items? I can think of a couple - CDC & maybe XE live target. I'm not sure what the best option is for excluding these. Maybe based on wait type - excluding WAITFOR and XE_LIVE_TARGET_TVF. |
So in any env you know there are certain reports or monitoring tools or
jobs that run a lot and clutters DBADash long running query which is very
useful. It would be good to have an option to make an exception for those
so they don't show up there or expand the long running query list limit.
…On Thu, Oct 10, 2024, 3:09 PM David Wiseman ***@***.***> wrote:
What criteria would you like to use to exclude items?
I can think of a couple - CDC & maybe XE live target. I'm not sure what
the best option is for excluding these. Maybe based on wait type -
excluding WAITFOR and XE_LIVE_TARGET_TVF.
—
Reply to this email directly, view it on GitHub
<#1061 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BGN5RX2LMPXVW47IN242L7TZ233K5AVCNFSM6AAAAABPWV2XPSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBWGEZDMOJSGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Hi @DavidWiseman My personal expectation is for this filter to work on Running queries(Longest Running Query column) |
Can we add exception for long running queries for DBADASH? there are queries and processes that we always know take time and we want them to be excluded from the long running query report which is really useful.
The text was updated successfully, but these errors were encountered: