Currently when you apply AppInsight for SQL, all databases, including default databases like MSDB, model, etc are selected. We would like to be able to select which databases we monitor.
This is already possible today, albit it in reverse. Once AppInsight for SQL is applied, simply unmanage the Databases you don't wish to monitor. This will remove any status and prevent them from alerting.
I thought I looked this over in detail before posting this but I didn't see where I could unmanage specific databases. Can you point me in the right direction please?
It's located on the Database Details view for each database
I know this issue was resolved over 8 months ago, but I just installed SAM 6.2 and imported the AppInsight for SQL on my SQL server. Unfortunately I cannot, for the life of me, find where to unmanage the databases. I've been looking for the "Database Details" view as you listed above but I don't know where to find it.
Click on the name of the Database from the "All Databases" resource located on the AppInsight for SQL Application Details view as shown below.
http://oriondemo.solarwinds.com/Orion/APM/SqlBlackBox/SqlBlackBoxApplicationDetails.aspx?NetObject=ABSA:115
Thanks for the quick response. I feel a lot better with your response, because that was exactly what I was doing. The issue for me to now troubleshoot is whyI am receiving this error for the majority of my databases. Thanks.
.
Looks like this may be an issue with the settings for your user account that is outlined in the following KB article.
Perfect workaround! That resolved the issue immediately and gave me access to the databases and metrics! Thanks for help and support on this; you have been a life saver!
When I try and unmanage a specific SQL performance counter it in turn unmanges all of the performance counters in there a way to only unmanage one?
It is not possible to unmanage a specific component in SAM. You can however remove the warning and critical thresholds so they do not alert. That should provide the desired result.
All I ever see which this module is a sea of errors and warnings even for servers that have ZERO databases running or 10 databases running. I can't depend on the status since it always "thinks" something is wrong.