CIM vs. WMI as native 'Source type
Has anyone heard if LM has any plans in place to make the move from WMI to CIM for metrics grabs in general and Windows in specific?
https://thinkpowershell.com/powershell-and-common-information-model-cim-the-successor-to-wmi/
Cole McDonald
Posted 1 year ago·Last reply 1 year ago
6 comments
Joe Williams
·1 year agoI would wish for CIM as it would allow for PowerShell CLI on Linux and make allowing a Linux collector that monitors Windows possible.
Cole McDonald
OP1 year agoThat would remove the Windows License tax for adding collectors to customer enviornments... which isn't a huge deal for in-house monitoring... but as an MSP, we have to have a collector for every client of ours. So the costs scale quickly.
Barb Ramirez
·1 year agoHi Cole
I have actually created 2 Datasources one for CPU and one for Uptime using CIM as I find an error with WMI (invalid class) on these 2 fairly often that even thou we run through all the fixes it still doesn't get resolved. Then CIM is the answer. Would be handy to have a whole suite of Datasources in CIM for sure :)
Patrick Rouse
·1 year agoIf you don't mind, please provide an example of an official module that uses WMI rather than and what data collection change you'd like to see? Are you perhaps referring to modules like "WinSystemUptime" that uses the WQL_Query WMI Data Collection type with the the Win32_PerfRawData_PerfOS_System class?
Please let me know and I'll look into this for you. Thanks.
Barb Ramirez
·1 year agoHi Patrick Sorry for the delay I have been very busy. Yes we are talking about WinSystemUptime and CPU and memory and anything else that can be retrieved with CIM instead of WMI.
Barb Ramirez
·1 year agoI have this basic CIM one for uptime
Locator
AACZFJ
simply using
(get-date) - (gcim Win32_OperatingSystem).LastBootUpTime