Performance Trigger


Triggers the task when a system or process threshold (such as CPU utilization and memory usage) is met. The Performance trigger is ideal for monitoring servers in a "back office" environment. For example, if available memory is too low, a task can automatically restart the entire system or specific processes using the Restart computer or Start process activity. In the above scenarios, the entire process is automated, eliminating the need for human intervention. Additionally, this trigger has the capability to monitor system performance on a remote computer as long as that computer resides on the same network as the computer where AutoMate is installed. Specifying the remote system to monitor is as easy as entering the remote machine’s Host name or IP Address.

NOTE: AutoMate gathers the same system information used by Windows Performance Monitor (perfmon.exe).

Practical Usage

Used to monitor a server or workstation for certain performance characteristics or thresholds. This trigger is ideal for monitoring servers in a "back office" environment.

Example 1: Using the Performance Watcher trigger, if available memory is to low - the entire system or specific processes could be automatically be restarted.

Example 2: If disk space is too low, a notification message could be sent to the system administrator.

The Performance trigger generally uses the same powerful and intelligent system performance detection capabilities and gathers the same comprehensive hardware and system information used by Windows Performance Monitor (perfmon.exe), whereas, system performance is based mainly on performance counters, which are essentially measurements of system state and/or activity. They can be included in the operating system or can be part of individual applications.

Related Topics  





Use Local Computer

If enabled, the trigger will monitor performance on the local machine (enabled by default).

Use Remote Computer

If enabled, the trigger will monitor performance on a remote machine (disabled by default). To specify the remote machine, enter its Hostname or IP Address in the field provided. If this parameter is enabled, the Use Local Computer parameter is ignored.


The system category in which to monitor (i.e. Processor, Memory, Paging File, etc.). A category catalogues performance counters in a logical unit.


The counter related to the category in which to monitor. Performance counters are combined together under categories. They are used to measure various aspects of performance, such as transfer rates for disks or, for processors, the amount of processor time consumed. Specific counters are populated in this section depending on the system performance category selected.


The instance related to the category in which to monitor. A performance counter can be divided into instances such as processes, threads, or physical units.

Trigger when

Specifies the performance threshold and duration to monitor as it relates to the Category, Counter and/or Instance values selected.

Show Description

If enabled, a detailed description will appear for each selection.




Trigger on startup if condition is true

If enabled, the system will act upon conditions that already exist upon startup of the current trigger. For example, if the Notepad window is already open on the desktop, a newly created Window trigger set to monitor for the existence of a Notepad window will immediately launch the task as a result. If disabled, the trigger will ignore the open Notepad window upon startup. This parameter is disabled by default.

Trigger after the condition has been met 'X' times.

If enabled, specifies how many times the trigger condition must be met before the task is started. For example, if a Window trigger is set to monitor for the appearance of a Notepad window and this parameter is set to 3, the task will not launch until the third instance of Notepad appears on the desktop.


additional notes


When this trigger is activated, it automatically passes the AMTrigger object to the task. AMTrigger is a standard AutoMate dataset and can be used much like the datasets created by the SQL Query and Email actions. The fields of AMTrigger can be used within a task to determine specific values, such as whether or not the task was started by a trigger, which trigger started the task, when the trigger was activated and other properties. AMTrigger populates a unique set of field–value pairs for each AutoMate trigger. The following table lists the ones specific to this trigger. For more details about a specific AMTrigger field–value pair, click the associated link.


Data Type

Return Value



Returns the unique ID of the process that caused the trigger to activate.



Returns the unique ID of the thread that caused the trigger to activate. This is dependent on if the trigger is monitoring for a specific thread threshold (i.e. thread state).



Returns the value of the parameter that caused the trigger to activate.


NOTE: A full list of AMTrigger objects exclusive to each trigger can be viewed from the Expression Builder by expanding Objects -> Triggers and selecting the desired trigger.