In the SQL 2017+ Management Pack is a Monitor to monitor the free DB log space in percent. We would like to monitor the free DB log space additionally in MB. We need this because we have very much DBs, and they are from very small to very big. Its to much effort to set for every DB another percent treshold. And if we set a threshold 10%, this is good for small DBs, but if we have a big DB, there is no problem when free space is for example 10% but still 100GB. So we wanna set a threshold in percent to generate a warning. And we wanna set a critical treshold in MB, so we can generate an alarm, if there is really a low DB log space.

The 2014 and 2016 SQL Integration packs have "Discover SQL Server 2014 DB Installation Source (seed)" discoveries that are targeted toward the "Windows Server" class. In environments where SSIS may be installed on SQL Clusters (and SCOM has the clustering MPs imported), this can lead to duplicate instances of the Integration services being discovered. Clustered resource "servers" are also populated into the "Windows Server" class. I creates groups populated with "Windows Server" objects with the "Is Virtual Node" property set to "True", and override the discoveries using these groups. Pan Optional MP could be included that would be imported if you are using Windows cluster in your environment, that would great the groups automatically and override the discoveries to prevent clustered "Servers" from discovering as integration services.

Current SQL Management Packs provide reactive insight/notification into issues with mirroring, but there are no automated recoveries/ability for automated proactive maintenance when an issue is discovered. Mirroring outages require custom code, or manual intervention to resolve. This translates into added cost for customers in terms of in-house development, or if a recovery is manual it means longer outage durations.

Request is for a monitor that looks at the current state of mirrors + a automated recovery which executes a RESUME for any mirrors that are DISCONNECTED, SUSPENDED or UNSYCHRONIZED. It then should wait to give the mirrors a chance to CONNECT and then recalculate the health state of the mirrors again. Alert will remain open if the mirrors current status is anything other than SYNCHRONIZED or SYNCHRONIZING.

The 2014 and 2016 SQL Integration packs have "Discover SQL Server 2014 DB Installation Source (seed)" discoveries that are targeted toward the "Windows Server" class. In environments where SSIS may be installed on SQL Clusters (and SCOM has the clustering MPs imported), this can lead to duplicate instances of the Integration services being discovered. Because clustered resource "servers" are also populated into the "Windows Server" class, they too discover SSIS instances. In one example here, one cluster that only has two base nodes had five different SSIS instances discovered, when only the base nodes should be discovered. I had to create groups populated with "Windows Server" objects with the "Is Virtual Node" property set to "True", and override the discoveries using these groups. I realize that the MP can't be written assuming the cluster MPs are present in the environment, but perhaps an Optional MP could be included that would be imported if you are using Windows cluster in your environment, that would great the groups automatically and override the discoveries to prevent clustered "Servers" from discovering as integration services.