Performance Trigger

See Also

Introduction to Triggers, Available Triggers, Using AMTrigger, Setting a Performance Watcher Trigger


Triggers the task when a system or process threshold (such as CPU utilization and memory usage) is met.

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.


General Tab


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. To specify the remote machine, enter its Hostname or IP Address in the field provided.



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



Specifies 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.



Specifies 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.


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


Behavior Tab

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 trigger the task as a result. If disabled, the trigger will ignore the open Notepad window upon startup.

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 (disabled by default). This parameter is available in all triggers except the Schedule Trigger.

AMTrigger Parameters

When this trigger is activated, it automatically passes the "AMTrigger" object to the task. AMTrigger can be used within a task to determine whether or not the task was started by a trigger, which trigger started the task, when the trigger was activated and other trigger related properties. For more details, see Using AMTrigger.

Common AMTrigger Fields


Every instance of AMTrigger populates a list of common fields which are described in the table below.



Data Type

Return Value



Returns the name of the event or condition that triggered the task. Each event or condition contains a unique name. For this trigger, the value is always AMPERFORMANCETRIGGER.



Returns the name of the managed task that the trigger was attached to. Useful to determine the responsible task when two managed tasks point to the same AML file.



Returns the date and time when the trigger occurred.



Returns the machine name where the trigger occurred.



If the workstation was locked when the trigger occurred, the value returned is 1. Otherwise, it will be 0.



If the workstation was logged off when the trigger occurred, the value returned is 1. Otherwise, it will be 0.



Returns a verbose set of information about the triggered event or condition in AML (AutoMate Markup Language) format.


Specific AMTrigger Fields


The AMTrigger field listed in the table below are specific only to the Performance trigger.



Data Type

Return Value



Specifies the unique Process ID that caused the condition to activate. This is dependent on if the condition is monitoring for a specific process threshold.



Specifies the Thread ID that caused the condition to activate. This is dependent on the condition properties.



The value of the parameter that caused the task to start. This is dependent on the trigger properties. For example, if the trigger is set to watch for total memory to drop below a certain threshold, this value will contain the total amount of memory below that threshold when the task triggered.


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.

See Also

Setting a Performance Watcher Trigger

About Triggers

All Available Triggers

Using AMTrigger