7 Replies Latest reply on Jan 13, 2015 6:27 AM by Steffen Kreis

    Using an EXO as a Component Template Discover condition

    Joe Piotrowski

      Are there any cons to using an Extended Object as a Discover condition in a Component Template?


      For example we are using the Running Processes (running_processes.nsh) extended object that comes with our content installation:



      It works fine for many servers (successfully creates the Component, successfully passes the discover condition and does not). However, many servers are throwing fork errors, or Out of Memory errors.


      I have an open ticket around that. But wanted to know if doing something like this is considered bad practice, or not a recommended way of using Discover conditions.


      Screenshots of successes and failures: