no, I agree with a master log file - this will benefit MSFT CSS Support Teams for scouring through multiple logs.
also, a recent history limit setting in the Client Settings.....so you can set this for example for 30 days and then the next month it will reset for the new updates.....
So basically instead of running 3 Configuration Manager Actions (Machine Policy, Scan and Software Evaluation), it does all the 3 in one go.
Building on that, a button next to the "Check for updates" button called "Update Logs" which opens the following logs [UpdatesDeployment.log, UpdatesHandler.log, ScanAgent.log, WUAHandler.log and the UpdatesStore.log] in CMTRACE and merged as one.
Better still, add a "Disable" right-click command in the Properties of the Collection just like Deployments which will stop evaluation and also a "Retire" right-click command so that SCCM admins can housekeep their collections.
You can create a report and add this to your dataset:
select distinct ObjectId from vSMS_ManagementInsightResultsList where QueryID='B585E3FF-585F-4CE9-AE2C-648A7CA2F143'
run this to grab the all the IDs and Names of the available Management Insight data:
SELECT ID,Name FROM vSMS_ManagementInsights
Even the skin needs an uplift - if we are going W10, then a lo-fi skin will look cool and less CPU hogging. No more skeuomorphic design but flat icons please :)