Comments
Sort by recent activity
@Alex B, Thanks for the response and the confirmation. PS looked like the best option for us and is what we'll be moving forward with. Thanks again, -Luke. / comments
@Alex B, Thanks for the response and the confirmation. PS looked like the best option for us and is what we'll be moving forward with. Thanks again,-Luke.
Rather than updating the alert suppression window in the database, I think we're going to go with just disabling this alert via the powershell module... for anyone else interested in this, the code will look something like this... We'll put this code in the first agent job step and the reverse in the last job step, with the DBCC CheckDB in between. <div>using module "RedgateSQM"</div><div><br></div><div>#Params</div><div>[string]$MonitorServer = "monitorservername"</div><div>[string]$ServerNameToUpdate = "myserver"</div><div>[string]$AlertName = "DiskReadTime"<br>[string]$Status = "Inherited" ## or "Disabled"<br></div><div><br>##Setup connection to sqlmonitor</div><div>$ErrorActionPreference = "Stop"</div><div>$MonitorServerURL = "http://$MonitorServer`:8080"</div><div>Connect-SqlMonitor -ServerUrl $MonitorServerURL -AuthToken "myauthtoken"</div><div><br></div><div><div>##Get the AlertType</div><div>$alertType = $AlertTypes.Contains($AlertName)</div><div><br></div><div>##Get the Monitored Object current alert settings</div><div>$MonitoredObject = Get-SqlMonitorMachine -Name $ServerNameToUpdate</div><div>$alertSettings = Get-SqlMonitorAlertSettings -MonitoredObject $MonitoredObject -AlertType $alertType </div><div><br></div><div>Write-Host "Current Setting: " $alertSettings.Status</div><div>##Make the update</div><div>Update-SqlMonitorAlertSettingsStatus -MonitoredObject $MonitoredObject -AlertType $alertType -Status $Status</div><div><br></div><div>##Get the updated settings</div><div>$alertSettings = Get-SqlMonitorAlertSettings -MonitoredObject $MonitoredObject -AlertType $alertType </div><div><br></div><div>Write-Host "Updated Setting: " $alertSettings.Status</div></div> Thanks, -Luke. / comments
Rather than updating the alert suppression window in the database, I think we're going to go with just disabling this alert via the powershell module... for anyone else interested in this, the code...
Alex, thanks for the reply... I'll work through it and see if I can make this work. Yes, I used that example code as a basis for a process where I was planning to pass in a machinename or cluster name as well as set the $isCluster parameter since I would know which were FCI and which weren't. The issue I ran into with the Cluster process was when I used Get-MonitoredObjectStatus to find the instances on a machine in the cluster, the first instance from the first machine, appeared with the second machine. i.e. 4 node FCI, with 4 instances. one instance per node on a normal day. Get-MonitoredObjectStatus was returning nothing for the first machine but 2 instances on the second machine. I'll try your code and let you know if this solves the problem for me. Thanks again, -Luke. / comments
Alex, thanks for the reply... I'll work through it and see if I can make this work. Yes, I used that example code as a basis for a process where I was planning to pass in a machinename or cluster ...
Alex, I had to make some changes to your code. All of the commandlets for my version of monitor powershell are named with the Keyword SqlMonitor... example: Get-SqlMonitorCluster vs. Get-Cluster from the documentation this is a version compatibility issue... we are running 10.0.11.28553. Based on other communication from RG, we won't be able to upgrade until after we complete a hardware refresh later this fall. Our base monitor is installed on a windows 2012 server slated for refresh in the next few months. With the cluster instances I am seeing the same issue as with my code. There is no status information returned for the first instance of a multi instance FCI. The default instance returns: (local) Successfully monitoring: Configuration state: Connection status error:
while the second instance returns NamedInstance Successfully monitoring: True
Configuration state: Monitoring
Connection status error:
The default instance returns nothing or NULLs? while all named instances return the expected information. Is this an issue because it's a default instance on a cluster? Thanks, -Luke. / comments
Alex, I had to make some changes to your code. All of the commandlets for my version of monitor powershell are named with the Keyword SqlMonitor... example: Get-SqlMonitorCluster vs. Get-Cluster ...
Hello and thanks for your response. It appears this feature has been requested since 2013... https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/4359531-alert-when-sql-monitor-is-having-a-problem I just up-voted it. The issue in the above link is exactly what we recently faced. The SQL instance hosting the Data Repository database became unavailable, but no alerts were fired. The instance was in an unavailable state for around 10 minutes before the cluster service was able to stop it and then bring it back online. We would have liked to have notified that one of our mission critical instances was having trouble. Thanks, -Luke. / comments
Hello and thanks for your response. It appears this feature has been requested since 2013... https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/4359531-alert-when-sql-monitor-is...
Hello and thanks for your response. It appears this feature has been requested since 2013... https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/4359531-alert-when-sql-monitor-is-having-a-problem I just up-voted it. The issue in the above link is exactly what we recently faced. The SQL instance hosting the Data Repository database became unavailable, but no alerts were fired. The instance was in an unavailable state for around 10 minutes before the cluster service was able to stop it and then bring it back online. We would have liked to have notified that one of our mission critical instances was having trouble. Thanks, -Luke. / comments
Hello and thanks for your response. It appears this feature has been requested since 2013... https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/4359531-alert-when-sql-monitor-is...
Hello and thanks for your response. It appears this feature has been requested since 2013... https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/4359531-alert-when-sql-monitor-is-having-a-problem I just up-voted it. The issue in the above link is exactly what we recently faced. The SQL instance hosting the Data Repository database became unavailable, but no alerts were fired. The instance was in an unavailable state for around 10 minutes before the cluster service was able to stop it and then bring it back online. We would have liked to have notified that one of our mission critical instances was having trouble. Thanks, -Luke. / comments
Hello and thanks for your response. It appears this feature has been requested since 2013... https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/4359531-alert-when-sql-monitor-is...
Hello and thanks for your response. It appears this feature has been requested since 2013... https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/4359531-alert-when-sql-monitor-is-having-a-problem I just up-voted it. The issue in the above link is exactly what we recently faced. The SQL instance hosting the Data Repository database became unavailable, but no alerts were fired. The instance was in an unavailable state for around 10 minutes before the cluster service was able to stop it and then bring it back online. We would have liked to have notified that one of our mission critical instances was having trouble. Thanks, -Luke. / comments
Hello and thanks for your response. It appears this feature has been requested since 2013... https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/4359531-alert-when-sql-monitor-is...
That's great news. I'm not sure how quickly we'll be able to get the next release installed since we just did an update, but I'll pass this along. I'll let you know when we get it installed if we still see the issue. / comments
That's great news. I'm not sure how quickly we'll be able to get the next release installed since we just did an update, but I'll pass this along. I'll let you know when we get it installed if we...
Alex, We've upgraded to version 9.1.3.23063. I'm still unable to stop blocking alerts from some SSRS processes, and I'd appreciate some guidance. I've added the following to both of the exclude boxes for that instance but still get the blocking alerts for very long running reports. CheckSessionLockWriteLockSession Below is a screenshot of the alert. As you can see the database Name is still unknown, however the blocking SQL fragment contains the writelocksession procedure, and the Blocked SQL Fragment contains CheckSessionLock, so I would think the above would work. Please let me know if you have any ideas. Thanks, -Luke. [image] [image] / comments
Alex, We've upgraded to version 9.1.3.23063. I'm still unable to stop blocking alerts from some SSRS processes, and I'd appreciate some guidance.I've added the following to both of the exclude box...