Administration Guide › Managing SystemEDGE and Application Insight Modules (AIMs) › How to Configure SystemEDGE and Service Response Monitor Through Policies and Templates › How to Create and Apply an Autowatcher to a System › How Autowatchers Work › Process and Service Autowatchers

Process and Service Autowatchers

Use Process and Service Autowatchers to create process and service monitors dynamically.

A Service Autowatcher creates multiple service monitors in the process table whenever a service matches an Autowatcher criteria (service name, start type, and so on). For example, you can monitor all installed the SQL services with a start type as ‘automatic’.

A Process Autowatchers create process monitors in two ways:

• Using a process name (default) - When a process name matches the Autowatcher criteria.

  For example, a process monitor is created when a process matches a criteria of process name of ‘sql’ or ‘svchost’. Autowatcher-created process monitors track a matching process that currently runs on a managed system, regardless of PID.

  • Autowatcher-created process monitors have the same semantics as manually created process monitors.
  • You can individually monitor a set of processes with the same name, but different arguments. For example, “java.exe”.
  • You can create monitors for a set of related processes.
• Using PID - When a PID matches the Autowatcher Criteria. The Autowatcher enables the Monitor Process using the PID flag in the user interface or specifies the watch flag 0x1000 in the sysedge.cf file.

  Each Autowatcher-created monitor tracks all matching instances of a process.

  • Creates monitors for particular instances of processes.
  • Monitors multiple instances of a process with no distinguishing arguments.

More information:

How Autowatchers Work