Good article. But, OpsMgr is not as accurate and trust worthy as it has to be. I implemented it couple of weeks back and even though my dev two servers are down for network issue for more than 24 hrs, it still showed me as "healthy", which was not.
But, I agree it does reduces some efforts of DBA but not all.
In a recent MS survey I gave it a 6 out of 10 as a product. Yes, there is definitely a lot of room for improvement. We have recently had to re-install the whole thing because the OpsMgr agents were not working properly and SQL job discovery was not working! I spent an enormous amount of time trying to get the thing to work, even with help from MS support!
So, yes, in my opinion, the product is not on the same level of quality as SQL Server at this point. But the premise I think is there, and the more we all use it the better it will be in future versions.
For one thing, its customization features, along with introduction of powershell, are very promising.
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]