AdvisorAdvisor13 minutes ago, Stuart Weenig said:Have you looked at mine? https://github.com/sweenig/lmcommunity/tree/master/ProcessMonitoring/Linux_SSH_Processes_Select
Duplicate processes with the same command line and same name will be a problem if you're ignoring PID. Under manual circumstances, how would you differentiate between the two between sessions? I mean, if you logged in once and looked and saw process A and process B. Then if you logged in again 1 minute later and saw the same list of processes, how would you know which was you had previously called A and which one was previously called B?
The answer is, of course, to run them in separate containers, but that's a different discussion.
Yeah I looked into your example but, that has the PID as wild value.
That's exactly the tricky part of this. Cause nowadays our probe is able to catch those processes (even with same name) & alarm if those get stopped. I just don't know how to replicate this at LM.
Was wondering if anyone might come up with a workaround that I'm not actually seeing.
I've tried to come up with something that has the cmdline & then enumerating those as cmdline#1/#2 etc... but, if now there's 3 instances of the process running but later there's only 2... the third instance will return an alarm (cause we don't want to erase it, since we want historical data).
I guess our only solution would be asking the client how many processes should be running with that cmdline & alert if those are lower than the expected.
But this is downgrading the monitoring we're doing for him nowadays 
