User Event Emulation Agent Templates

There are three types of agent templates in the User Event Emulation agents category: Class ME Variables, Link ME Variables, and Partition ME Variables. These agents monitor a measurement (ME) variable of your choice on a traffic class, link, or partition of your choice. Over 130 measurement variables are available. User Event Emulation agents do not appear on a unit or PolicyCenter configuration by default, but must be manually created. Each User Event Emulation agent is defined by a different set of parameters that determine what is checked, and how the results are reported. The specific parameters for these agents are described in the table below.

Note: An alternative way to monitor a specific class, link, or partition and receive notification when a threshold crossing has occurred is with the event notification feature. Although events created with the event new command have functionality similar to User Event Emulation agents, they cannot be monitored with the adaptive response feature.

Parameter
Value
ClassName

The name of the class, partition or link to be measured (for example, /Inbound or /Outbound/default)

Note that Partition Utilization agents can only specify the class name of a link or traffic class with a partition; setting a Partition Utilization agent for a class or link without a partition will cause an error. For Default Traffic agents, you must specify the class name of default traffic classes, such as /Inbound/Citrix/default or /Outbound/HTTP/default.
MeVariableName
The measurement variable to be monitored. Each measurement type — link, partition, and class — has its own set of variables. The default value is bytes, but any measurement variable of the appropriate type may be used. See a complete list of measurement variables.
MeDuration
The period of time over which measurements will be taken, in minutes.
RedOperator

When you configure a red threshold for a User Event Emulation agent, you must also enter a RedOperator parameter. Use one of the following values:

  • LT — Agent has a red status when the current value of the measurement variable is less than the RedThreshold value
  • LTE — Agent has a red status when the current value of the measurement variable is less than or equal to the RedThreshold value
  • GT — Agent has a red status when the current value of the measurement variable is greater than the RedThreshold value
  • GTE — Agent has a red status when the current value of the measurement variable is greater than or equal to the RedThreshold value
  • EQ— Agent has a red status when the current value of the measurement variable is equal to the RedThreshold value
GreenOperator

When you configure a green threshold for a User Event Emulation agent, you must also enter a GreenOperator parameter. Use one of the following values:

  • LT — Agent has a green status when the current value of the measurement variable is less than the GreenThreshold value
  • LTE — Agent has a green status when the current value of the measurement variable is less than or equal to the GreenThreshold value
  • GT — Agent has a green status when the current value of the measurement variable is greater than the GreenThreshold value
  • GTE — Agent has a green status when the current value of the measurement variable is greater than or equal to the GreenThreshold value
  • EQ— Agent has a green status when the current value of the measurement variable is equal to the GreenThreshold value
RedThreshold
The value at which the status of the agent turns red, and a red action file is triggered, if present
GreenThreshold
The value at which the status of the agent turns green, and a green action file is triggered, if present

 

 

        

PacketGuide™ for PacketWise® 7.4