Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Report for missing polling information

In a few instances, I have noticed CPU/memory polling has stopped for a node. I don't know why it happens, but it is a simple fix -- remove the resources from polling, add them back and it starts polling again. This has happened three or four times and I found it each time when I was looking at a specific node.

However, I don't look at every single node with regularity. So, there could be more nodes out there that have stopped polling. What I want is a report that would tell me if a node has stopped compiling these stats. Otherwise, I will only find it when I look for it, which means I will only find it when I need it.

I have found reports for reporting cpu/memory but to my knowledge, these reports will use the last measured value, which means if it has stopped compiling stats, it will just use the last one it measured.

Anyone have an idea of how I could accomplish this?

Find more posts tagged with

Reports

Accepted answers

sum_giais

Hi @nafeeskhan29 do you have any links to provide for details around what you've mentioned to help @kpourmand?

@kpourmand:

Have you opened a support case on this? (perhaps the next time you see this if you havent already, open a support case and use it as an opportunity to triage / provide diags)
What Polling methods are the nodes this is occuring on? Any correlation there?

There's a couple recommendations I have...

Create a node polling failure alert: https://thwack.solarwinds.com/content-exchange/the-orion-platform/m/custom-queries/3028, this can additionaly be used to create a widget in an admin view for real-time review.
Leverage the 2 built-in alerts for engine polling failures: "No polling engine update in last 10 minutes" & "Node polling failed on last 5 tries"
I think there's certainly merit to @nafeeskhan29's points above but I'd very much stress to work with support prior jumping in and doing any repairs of that nature.

Now that may not cover the issue you're seeing, there's also the potential that maybe a duplicate cpu/mem poller exists which you can use the below query to determine that.

thwack.solarwinds.com/.../3022

All comments

nafeeskhan29

1. Manually poll the device and check if data got collected or not if yes then apply below solution

2. Need to replace SDF Job engine and Collector files and check if stats are getting collected or not

3. Also Script is available on thwack which shows the nodes on stats are not collected for more than 30 mins

sum_giais

Hi @nafeeskhan29 do you have any links to provide for details around what you've mentioned to help @kpourmand?

@kpourmand:

Have you opened a support case on this? (perhaps the next time you see this if you havent already, open a support case and use it as an opportunity to triage / provide diags)
What Polling methods are the nodes this is occuring on? Any correlation there?

There's a couple recommendations I have...

Create a node polling failure alert: https://thwack.solarwinds.com/content-exchange/the-orion-platform/m/custom-queries/3028, this can additionaly be used to create a widget in an admin view for real-time review.
Leverage the 2 built-in alerts for engine polling failures: "No polling engine update in last 10 minutes" & "Node polling failed on last 5 tries"
I think there's certainly merit to @nafeeskhan29's points above but I'd very much stress to work with support prior jumping in and doing any repairs of that nature.

Now that may not cover the issue you're seeing, there's also the potential that maybe a duplicate cpu/mem poller exists which you can use the below query to determine that.

thwack.solarwinds.com/.../3022

kpourmand

Any idea where that script is? I can't find it.

kpourmand

The first time, I did talk to support and their solution was to remove/re-add it. I will look at your links. Thanks.

bobmarley

Another reason to check out the posts on Thwack Followed @sum_giais link and found a few misconfigured nodes.

kpourmand

I followed his link and the results I'm getting don't make a lot of sense. It is listing nodes that supposedly haven't polled and yet when I look at them in solarwinds, they have polled.

sum_giais

I apologize in advance for the questions but... Can you clarify what polled? Cpu? Mem? Status? All of it? Is it current? What polling method? Any corellation between any and how many show on the list? Are there issues with the assigned pollers? Maybe a wmi poller assigned to linux or something strange? Does performing a test of the credentials if wmi or snmp succeed when editing the node? Does the agent status look Ok?

If they show on that list (the polling failure custom query list that is) there's usually "something" wrong with the configuration. Not always presenting in the same way... I've seen agents poll status cpu and mem data but stop updating the systemuptime for some reason or another, restarting the agents fixed that.

kpourmand

There may be something else with those devices. I did just a quick glance at the main node page and didn't see anything wrong, except for one device that appears to not have been set up correctly. So maybe there is something else going on with each device. I will take a closer look.

kpourmand

Ok, so there were two virtual machines in the list, both agents. I unmanged and then re-managed each and they disappeared from the list.

Now the list makes more sense. Every device left either has a problem or has been unmanaged for a while. It was confusing because most of the devices are still compiling stats. For example, one device says it hasn't updated since Sept 1. But I have CPU/Memory data from just a few minutes ago. Then I realized it might be pulling the data from vcenter, as this is a vmhost. Sure enough, the snmp is not working for the host. It was recently upgraded, so I guess it needs to be set again.

So it does look like it is working. Idk why the first two were "stuck" but as long as it doesn't happen all the time, I'm fine with that.

Thank you for the help!