NOTE:
Actions attached to process-monitor policies can make use of
session variables, which are illustrated in the examples below and
described in more detail in Policy
variables.
The default actions which are defined for the process-monitor policies are:
<$NAME>:<$MSG_NODE_NAME>:<$MSG_OBJECT>:START
<$NAME>:<$MSG_NODE_NAME>:<$MSG_OBJECT>:<*>
<$SESSION(PROCESSNBRAVAILABLE)> processes
"<$SESSION(PROCESSNAME)>" with parameter
"<$SESSION(PROCESSPARAMETERS)>" are running. Expected:
<$SESSION(PROCESSMODE)> <$SESSION(PROCESSNBREXPECTED)>
process.
Example: 0 processes "notepad.exe" with parameter
"<*>abc<*>" are running. Expected: 1
process.
No "continue" action is defined: do NOT start any "continue" action
<$NAME>:<$MSG_NODE_NAME>:<$MSG_OBJECT>:END
<$NAME>:<$MSG_NODE_NAME>:<$MSG_OBJECT>:<*>
<$SESSION(PROCESSNBRAVAILABLE)> process
"<$SESSION(PROCESSNAME)>" with parameter
"<$SESSION(PROCESSPARAMETERS)>" is running.
Example: 1 processes "notepad.exe" with parameter
"<*>abc<*>" is running.
Related Topics:
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.