Looks like for some reason the data has been removed from the DB. Get to the node Manage nodes -> Search for the Node, do a list resources remove/uncheck the existing resources (Hardware Health) from there and hit on submit.
Again continue the same process till list resource and re-add/check Hardware Health and hit on submit.
This would add the latest sensors detected back onto the DB. Check for the same sensor once you perform these steps.
Hope it helps.
Get to the node Manage nodes -> Search for the Node, do a list resources remove/uncheck the existing resources (Hardware Health) from there and hit on submit.
"Manage nodes" doesn't allow me to search for hardware resources or sensors. So, what am I searching for, in "manage nodes"? I.e. how do I find out which node it is?
I can probably figure out how to list all nodes with hardware sensors, and then list resources on each one to see that it might have been one that triggered the alert. Will I know for sure?
In addition, I should modify the default alert to include node info, and then wait for the alert to get triggered again. Not the answer to my question, regretfully.
Dear Solarwinds: shouldn't node info be included in the default alert, by default, for cases like this?
Seems that this is either a result of a corrupted database, or a combination of several bugs in Solarwinds?
If the record (of an object in Solarwinds) is stale and no longer exists, why was the alert triggered?
If the object does exist, and the alert was triggered correctly because of an issue with it, then Solarwinds' behavior must be a bug on two counts: (1) the alert points to a non-existent record, (2) does not offer any other way to track the issue (e.g. the node ID)
...and the database being corrupted is unlikely because SW runs integrity checks once a day, if memory serves me right?
You will to dig them in DB - hardware details are spread across APM:HardwareXXXXXX tables you will find the node id that is linked to from those tables
Below links might give you a better understanding on the same:
Hope it helps