Unix File System Monitoring

Provided SNMP is enabled and configured on the Unix host you should be able to list resources on the node and select the volumes you want to monitor as pictured below.

Hi,

I'm using Linux agent to monitor one of the Linux servers using NPM. However, the / file system is not getting monitored. The data is not collected for / and when I do "list resources", I could see that the "/" is not selected. If I try to select and submit and then again do "list resources" I could see that / is still not selected for monitoring.

Could someone please help?

aLTeReGo 

---

Deepthi wrote:

Hi,

I'm using Linux agent to monitor one of the Linux servers using NPM. However, the / file system is not getting monitored. The data is not collected for / and when I do "list resources", I could see that the "/" is not selected. If I try to select and submit and then again do "list resources" I could see that / is still not selected for monitoring.

Could someone please help?

aLTeReGo 

---

Out of curiosity, what version are you currently running in your environment? This issue appears to have been solved in the latest release under internal case DC-604.

Hi aLTeReGo ,

I'm using  NPM 12.3 and I do not see the issue with same version of NPM in another instance of Solarwinds Orion.

Agent version: swiagent-2.0.0.70-857826

Thanks,
Deepthi

The issue is specific to the node being monitored via the Agent. If you were to have that other NPM instance monitor that same machine using the Agent, you would see the exact same thing you are now. 

The issue has to do with how that machine is returning volume indexes to the Agent. This is a known issue that is resolved in the latest release, but is not broadly applicable to all Linux machines. In fact, this likely affects less than a single percentage of all monitored Linux machines. 

The issue is specific to the node being monitored via the Agent. If you were to have that other NPM instance monitor that same machine using the Agent, you would see the exact same thing you are now. 

The issue has to do with how that machine is returning volume indexes to the Agent. This is a known issue that is resolved in the latest release, but is not broadly applicable to all Linux machines. In fact, this likely affects less than a single percentage of all monitored Linux machines. 

Hi aLTeReGo 

Thank you for the update. So is it addressed in the latest version of NPM or agent? Is there any hotfix as I will not be able to upgrade NPM. Is there any other solution to address the issue?

Thanks,

Deepthi

I'm afraid not. Compatability for the Orion Agent is tied to its version of the Orion Platform. 

There is some good news, however. There have been an absolute ton of improvements made since 12.3. Especially around installation and upgrades, as well as website performance. If you're under active maintenance, you'd be absolutely remiss if you weren't taking advantage of these and many more new capabilities. 

• https://documentation.solarwinds.com/en/Success_Center/NPM/Content/Release_Notes/NPM_12-4_Release_Notes.htm#New
• https://documentation.solarwinds.com/en/Success_Center/NPM/Content/Release_Notes/NPM_12-5_Release_Notes.htm#NewFeaturesNPM
• https://documentation.solarwinds.com/en/Success_Center/NPM/Content/Release_Notes/NPM_2019-4_Release_Notes.htm#NewFeaturesNPM
• https://documentation.solarwinds.com/en/Success_Center/NPM/Content/Release_Notes/NPM_2020-2_Release_Notes.htm#NewFeaturesNPM

Thank you aLTeReGo  for all the updates and quick responses. 

I guess, I need to let go of the monitoring of "/" for this particular server.

Any particular reason you won't upgrade?