I am wanting a report on uptime and was wondering if there was a way to do that. All I can find is Last Boot, but I want uptime. Am I able to do this?
Hope below url help you.
Create a report in the SolarWinds Platform Web Console that displays device uptime
I do not think we have any option for uptime. Please check above link help you.
Check the below thwack link might help you
Uptime and Downtime Report - Forum - Network Performance Monitor (NPM) - THWACK
This seems to be a common ask - dating back more than a decade in various Thwack threads. Today I create reports using "last boot time" which can be in accurate based on SNMP agent or Solarwinds agent or WMI agent restarts. I also find that occasionally it is unreliable probably due to the underlying OS / SNMP agent. With so many folks asking for a solution to this problem, and it persisting so long, I am guessing it is not a simple solution. For windows servers, which I personally care the most about, we can get accurate data via powershell (systeminfo | find "System Boot Time") but I have no desire to remotely query that on several hundred nodes then aggregate the data then produce a report from it. My hope for a Solarwinds agent solution also seems problematic as the last boot time is either still tied to SNMP or the Solarwinds agent - not the OS uptime.
I believe you can also retrieve using (wmic path Win32_OperatingSystem get LastBootUpTime) but we use WMI sparingly so not a good fit for us and still presents similar challenges to powershell option and the formatting of this output is less desirable.
So a few facets to what you mention i think are driven by two historical patterns from Solarwinds as a company.
They have had a long history of not coming up with new data, your machines emit this data and SW can display it but we won't recalculate it or come up with new numbers/strings/whatever. Even in cases where there widely known bugs with vendor data in SNMP they just told people to take it up with the vendor, they are just going to display what the device tells us. It makes sense as it keeps them from being responsible for coding around other company's bugs.
The other facet is that the data model underneath for the most part tries to keep nodes as universally as possible, so if you have a data point that only exists for windows devices but would be empty for all network gear or linux boxes then they have historically been unwilling to add that as a column on the node table.
Your example of using powershell to pull it is good, and within the constraints of how SW likes things to work you should create that as a SAM powershell script monitor and assign it to your windows nows and it will live in the SAM tables which are a lot more dynamic in how they handle uniqueness. It would be pretty simple to create a report in SW that shows the output of that component across all servers that have that template assigned.Of course there have been a ton of staffing changes at SW since the acquisition and maybe the new architects and devs are open to new types of feature requests but over the years I have found that I got a LOT more done by just doing my own work within and sometimes around the model that SW devs have already built instead of holding my breath trying to get them to change on how they do things.
