Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Sometimes it is necessary to run plugins or local checks asynchronous. Here is a guidance on how to achieve this!

Step-by-step guide

  1. Required settings
    1. Set cache age for plugins and local checks
      1. A cache age limit on plugins and local checks. If set, the output of plugins is cached and reused until this much time has passed.
      2. Setup → Agents → Windows, Linux, Solaris, AIX → Agent rules → Set cache age for plugins and local checks → Edit rule: Set cache age for plugins and local checks


    2. Set execution mode for plugins and local checks
      1. Some scripts are slow and can therefore stall the execution of the agent. To remedy this, such scripts may be run asynchronously. With this rule asynchronous execution can be set on a per-script basis.
        1. Setup → Agents → Windows, Linux, Solaris, AIX → Agent rules → Set execution mode for plugins and local checks → Edit rule: Set execution mode for plugins and local checks


          About the pattern: The pattern (wildcards supported) by which to select the affected scripts.

          Now my mssql.vbs plugin will run asynchronously with a cache age of 600 seconds! 


  2. Optional settings
    1. Reloading...
      1. a
        1. SetupAgentsWindows, Linux, Solaris, AIXAgent rulesSet timeouts for plugins and local checksNew rule: Set timeouts for plugins and local checks
    2. New rule: Set retry count for plugins and local checks
      1. q
        1. SetupAgentsWindows, Linux, Solaris, AIXAgent rulesSet retry count for plugins and local checksNew rule: Set retry count for plugins and local checks


About the pattern: The pattern (wildcards supported) by which to select the affected scripts.


  • No labels