NeophyteOn 11/23/2022 at 7:15 PM, mnagel said:I was saddened to find that the developers rejected this fix to allow for optional argument matching, claiming it represents a desire on my part for "a wide reaching application monitoring solution". I feel like they have perhaps hit their collective heads, but I have no option but to never import that module again. And before anyone says "CSM" -- been there, no help (no response actually).
I have two DataSources I've attempted to put up on the Exchange that use Regular Expression to pick and choose with processes one monitors -- we've leveraged it to a large degree of success so far, and was the only favorable way I could find to leverage process monitoring via SNMP at scale. Here are the locator codes:
JDCMLM (SNMP version)
9YLFYE (SSH version)
These are presently under Security review (and have been since I uploaded them September 07, 2022), so I don't know if they're actually visible on the Exchange. Maybe @Stuart Weenigcan enlighten us to whether or not they're viewable while in Security Review ?
I will say that, as a matter of principle, checking process health by whether it's running or not really isn't appropriate -- it should only be viewed as a stop-gap. Querying the processes directly for their health is 100% the only correct path to take (though not always available). Anyone who argues that this type of monitoring constitutes 'wide-reaching application monitoring solution' really doesn't have an understanding as to what 'application monitoring' actually means, and I, too, would strongly question their motivation for making such an argument.
