Windows Service Not Running - SQL Server (SSRS Service Name Change)

Question

DPA has a built in alert for SQL server called "Windows Service Not Running - SQL Server". I had this setup for a group of servers running SSRS, which would look for the Server "ReportServer". It seems that Microsoft changed the actual service name in SQL 2019 to "SQLServerReportingServices", so this alert started firing stating that the SSRS service wasn't running. Just wondering if anyone has a better solution to this than having to create two different SSRS Server groups (one pre SQL 2019, and one for SQL 2019 and later). It doesn't appear that the alert allows for multiple Service Names. 
 Thanks!

fabian.s · Accepted Answer

Hi 
 
 As far as I know it is not possible to specify more than one service name in the alert. 
 You could create a feature request for that https://thwack.solarwinds.com/product-forums/database-performance-analyzer-dpa/i/feature-requests 
 
 A workaround idea is: 
 - Create rule A based on the version information which is gathered automatically by DPA. Version >= 15.0 
 - Create rule B . Version < 15.0 
 - Create alert C. Filter the "database instance" on rule A and checking for "SQLServerReportingServices" 
 - Create alert D. Filter the "database instance" on rule B and checking for "ReportServer" 
 
 With using the rules at least you don't have to manually assign monitored instances to groups. 
 All depends from your setup. 
 
 regards 
 fabian

Windows Service Not Running - SQL Server (SSRS Service Name Change)

Top Replies