Hi CPU on managed node due to Solarwinds.ServiceHost.Process using agent. Why is this spiking my devices cpu?
Hmmm. I've noticed a few other posts in the community indicating this same behavior.
adatole Do you know if this is a known issue by chance?
rgnetmon -
There's already a open thread on this issue, see SolarWinds Agent using 2-3+ GB RAM
I would also highly suggest opening a ticket with support on this issue.
Lastly, if you haven't upgraded/patched to Orion build 2018.2 Hotfix 6 do so. It might resolve your issue as it's resolved other peoples, although it didn't for us.
I have two categories of answers: "off the top of my head"; and "pass the buck"
"Off the top of my head"
Is this node being monitored by SAM? If so, is there a particularly intensive template applied to it. It could be an AppInsight template gathering a bunch of different metrics; or it could be a custom, user-created template that is running a non-optimized script.
Is the memory spiking all the time, or only at certain times (should be easy to track down, since node memory is a default statistic.). If it only spikes some of the time, then we need to investigate what else is happening on that box during that time. Is it during statistics collection? During some kind of cleanup routine? etc.
What's the disk space situation on the box. I have seen ALL SORTS of weirdness when the drive that houses the SolarWinds logs (\AppData\Solarwinds\logs) gets full.
Have you tried switching from agent-based monitoring to agentless for this node (assuming that's an option)? It would tell you whether the agent was the culprit or WMI in general or not.
Finally, is this just a single node, or all nodes you are monitoring with agents, or some of the nodes but not all, or some other group that might point to the common denominator?
"pass the buck"
aLTeReGo !!!
aLTeReGo is aware if, but if you haven't done so already open a support ticket so that they can track this issue.
bourlis and I were replying at the same time, but his answer was both concise and more correct than mine. Check out the other thread, open a ticket, and hang on for a fix.
Hotfix 6 is installed.
Thank you to everyone who opened a support cases regarding the issue outlined in this thread. Because of your assistance our engineering teams have identified the cause of the issue and are now actively working to develop a fix.
I like to use the agent since i tend to get better accuracy when it comes to polling, in my opinion.
Any updates on this fix? I recently installed Orion 2018.4 SAM 6.7.1 and I'm experiencing the exact same issue.
See Alteregos post from a few hours ago: https://thwack.solarwinds.com/message/411631?et=watches.email.thread#411631
An official hotfix has been released.
I installed the hotfix and this totally corrected my issue. Thanks so much for the help!
