Advisor
Neophyte1 hour ago, Austin Culbertson said:Looks like I was further along than I expected :)/emoticons/smile@2x.png 2x" title=":)" width="20" />
I've published both an SSH and an SNMP version:
Locator Code: 9YLFYE - LinuxRegexProcessMonitoring_withAD_SSH
Locator Code: JDCMLM - LinuxRegexProcessMonitoring_withAD_SNMP
Let me know if you have any problems locating these. These are the first datasources I've published, so I'm not sure the best way to facilitate it.
I can't figure out how to edit my post, so here's some additional guidance for how these work (which probably means it's already overly-complicated :)/emoticons/smile@2x.png 2x" title=":)" width="20" /> BUT, we have been entirely hands off with this ever since I wrote this 2 years ago, outside of adding a process here and there, so it works!
Active Discovery runs every 15 minutes and queries each device for all of its running processes.
The script pulls down the process.groupProcessesToMonitor and process.deviceProcessesToMonitor, and combines them with the universalProcesses to get a comprehensive list of processes for which to check devices.
The script indexes each running process by the configured regex, while also capturing the PIDs associated with all of the processes that are running
The script then combines the hrSWRunPath with the hrSWRunParameters to get the full process run string
The script then runs through each discovered process and uses a simple =~ to validate if any given process matches a process that is running on the device.
All discovered processes have a property associated with them that includes the PID in the property key, along with the run path of all matched processes.
PIDs which match the corresponding RegEx are added together, so that we can detect when a process restarts. This can be overridden by adding the exact same process regex to the 'process.universalProcessesRestartToIgnore' property
