Applications Systems

Unable to see Processes on Linux Orion Agent in SAM

This article covers how Linux Orion Agent monitors Processes in SAM, and to understand why it is not able to fetch information on the Process

First published date

4/23/2020 3:41 AM

Last published date

9/21/2022 6:44 PM

Overview

There are situations where you know that the process is running on the Linux server. But when you perform Real-time Process Explorer, or try to monitor the exact Process in SAM, you are not able to monitor that particular Process.

Product section

Server Application Monitor

Cause

Agent retrieves Process information by reading information about processes from /proc virtual filesystem (mainly these files: /proc/[pid]/cmdline, /proc/[pid]/io, /proc/[pid]/stat and /proc/[pid]/status). When reading it script runs elevated as root to have access to all processes and all collected metrics.

1. If you are able to see that the Process is working (maybe via netstat, etc.), you can take note of the PID
2. Using the PID, you can check in the /proc/ filesystem to ensure that it exists there. If the PID does not exists in /proc/ we are not able to see it
 

Resolution

1. Change the Node from Agent to SNMP, to rely on SNMP to get the Process instead of the Agent. That is assuming that SNMP is able to see the process. 

a. It is recommended that you first do a snmpwalk on the device - Verify device data for NPM and SAM using SNMPwalk
b. Thereafter, confirm that hrSWRunTable (1.3.6.1.2.1.25.4.2) contains the Process Name. If the Process Name does not show up in here, changing from Agent to SNMP will not make any improvement in the detection of the Process
** Changing Node from Agent to SNMP might cause statistics to be loss, as it is not possible to map certain parameters due to the different methods that they are polled.

2. Create a Linux script as a workaround to monitor the Process
** Support does not include development of custom scripts