Today I found the LoopMonitor class while replacing the Map<String, Object> parameter maps with something more intelligent.
I'm wondering what a use case of this monitor implementation could be. As far as I can see, the implementation uses the MonitorPlugin, which checks the interface address against a address pattern. For capsd, this makes perfectly sense - but used as a monitor, this reports an service as up if the interface address matches against the defined pattern. Is any use case for this behavior? greetings Dustin -- http://lab.sh
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev
_______________________________________________ Please read the OpenNMS Mailing List FAQ: http://www.opennms.org/index.php/Mailing_List_FAQ opennms-devel mailing list To *unsubscribe* or change your subscription options, see the bottom of this page: https://lists.sourceforge.net/lists/listinfo/opennms-devel
