nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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
Store

CPU and memory usage not being recorded

terrierjim

NPM has stopped recording CPU and memory statistics on all nodes since a few weeks ago. Other stats e.g. network latency and packet loss are still being recorded perfectly fine.

The 'live' CPU and memory charts/dials work fine too. It's just an issue when you click on one of these and want to look back in time.

I've been through various Solarwinds KB articles but they haven't lead to a solution.

This affects existing nodes and any new ones I add to the system.

I've attached a couple of screenshots showing the dials recording CPU and memory, but the underlying historical data missing.

Any advice is appreciated

Thanks

attachments.zip

Find more posts tagged with

Accepted answers

All comments

derik.pfeffer

@terrierjim,

I would check SNMP or WMI communication to these nodes. the gauges are miss leading as they will display the last collected statistic, which could be days or months ago. We actually removed them from our environments as well as those we work with because of this exact issue. There might have been a FW rule, ACL update, credential change if it happened across the board.

Best Regards,

Derik Pfeffer

Loop1 Systems: SolarWinds Training and Professional Services

LinkedIN: Loop1 Systems

Facebook: Loop1 Systems

Twitter: @Loop1Systems

rschroeder

One might expect a similar result if something has changed in your database retention of statistics. Check out Settings > All Settings > Details > Database Details. Look for the section that begins wtih "Retain Detail Stats" and see how long the details, hourly stats, and daily stats are retained. Verify your environment is saving the stats for the period you expect. If it's not, adjust it.

If it IS saving the stats the way you expect, then check out your actual snmp access by opening a node in NPM and editing it and using the Test button below the snmp section.

If snmp testing succeeds, you've got all the right snmp versions and community strings and access through firewalls and local ACLs. If it fails, fix the strings or version or firewall rules or ACLs on the nodes and test. Repeat the process until you get success in editing and testing the node's SNMP access from NPM.

If that doesn't fix it, and if other Thwack members' suggestions aren't getting the job done, do the following:

Collect the diagnostics on the problem poller(s)
While this is running, open an online Support case with SolarWinds. Select the appropriate priority for the case.
Once the case is opened online, upload/attach the diagnostics to it and notify the case owner via e-mail that they are attached (if you have a case owner yet).
Call SolarWinds support number and reference the case ID

Now you have everything the support engineer needs to start making progress on identifying and correcting the issue. AND you have the tech on the phone!

wandie64

Hello, I have the exact same issue. Since 1st Dec all CPU and Memory metrics have not been collected and the tables for this in the database have stopped generating. SNMP and WMI are working fine. I have a ticket open with Solarwinds and they are investigating. My second environment is working without any issues.

terrierjim

Hi Derik

Thanks for your reply. I've checked WMI connectivity by performing the test on the node management screen, and it passed successfully. The devices exist on the same VPLS network so I don't think it's a firewall issue.

terrierjim

Hi rschroeder

I checked the database retention and it looks fine. I've also tested the WMI connectivity via the node management page, which also works fine.

I've raised a ticket with support so hopefully they can get to the bottom of it.

jinwu

Has this problem been resolved? I had a similar problem where no historical data is available for all interfaces, The [dbo].[InterfaceTraffic] table is completely empty.

hpstech

Use the Orion server template to catch anomalies in stats/data collection.

If Results Notified error is high, interface collection and many other thintgs is most likely stalled.