alevybri

This is great, Blythe! A UI for creating managing these wait categories would be very helpful.

I had this issue recently with one of my monitoring services (I have three monitoring services (one for each domain in my org) feeding into one repository database). Restarting the monitoring service seemed to resolve it.

Correct, I want to exclude those waits. While running the query would let me exclude those wait types, isn't sys.dm_os_wait_stats cumulative? How would I rewrite this condition to check the difference between the last sample and current sample to calculate the ratio as seen here?

How is this query being executed? SQL Sentry monitors SQL Agent jobs and can alert on failure or unusually long/short job runtimes.

You can deploy the reports to an instance of SQL Server Reporting Services from within SQL Sentry (assuming you have the appropriate permissions in SSRS). This will eliminate the need to use the build-in report viewer and allow you to easily give a wider audience access to the reports.

First-line support is not in CONUS but I have a case open right now where they're working CONUS hours. If you can get escalated to the next level, I think you do get CONUS-based people and resolution usually (in my experience) comes rather quickly at that point.

I'm currently in the midst of a support case and baffled by the responses I've received. The initial response read as though the responder had only barely skimmed over my case. The two subsequent responses make me think that they're responding to a different ticket altogether - they're talking about a product which I not…

Procedure Stats is a separate collection from Completed Queries. I don't know offhand what the criteria are for what gets captured there. Procedure Stats is not what you asked about originally, and I would recommend creating a new thread titled appropriately to draw peoples' eyes to that very different question.

I think I need to pick up some Postgres knowledge this year.

Only queries with duration longer than 5 seconds are captured in Top SQL by default. You can change this threshold via Settings -> SQL Server -> Top SQL -> Collection Settings -> Minimum Duration.

Finally getting back to this. I had the Trace Engine set to Legacy, not sure if I'd tried changing it previously (or maybe it wasn't there until a service or client restart after I set the feature flag?). Now that I've switched it, I definitely see the XE sessions on my watched instances. Thanks!

I only made it to two in-person events this year. SQL Saturday Boston in October, and PASS Summit

I don't think I've seen this interface in SQL Sentry. How are you getting there?

I have seen this, but I think the only time I've seen this without a good explanation has been immediately after restarting the host VM

Did you need to restart the monitoring service again for "Collect Trace Events = False" to take effect? What is the XE session I should expect to see in SSMS?