The Tools section of the CommandCTRL application provides a comprehensive interface for monitoring and managing triggers and alarms associated with your machines. These triggers and alarms are visible in real-time and include historical data, enhancing your visibility and control over your environment.
Viewing and Customizing Triggers
Upon accessing the triggers, you may find that the default settings do not align with your specific needs. While system triggers cannot be modified directly (they can only be enabled or disabled), you can duplicate these triggers to create customizable versions. This allows you to tailor the conditions and behavior of the triggers to better suit your environment.
Editing and Creating Triggers
When you choose to edit an existing trigger or create a new one, you will be presented with several configuration options:
Details
-
Name: Assign a name to the trigger, which will be displayed in the trigger list.
-
Description: Provide a description for the trigger to clarify its purpose and conditions.
Conditions
-
Field: Select the metric you wish to monitor, such as CPU usage, memory load, etc.
-
Operator (Op): Determine the condition to evaluate, such as whether the metric is greater than or less than a specified value.
-
Value: Set the threshold that the metric must reach to activate the trigger. For instance, you might set this to 80% for CPU usage.
-
Interval: Define how many consecutive times the condition must be met before an alarm is triggered. This setting helps differentiate between transient spikes and persistent issues. For instance, configuring a trigger with a value greater than 80% CPU usage over 6 intervals means:
-
Real-Time: While in Real-Time mode only one 3 second interval is honored. For example, if the CPU usage exceeds 80% for one 3 second sample the violation will be highlighted.
-
History: The condition persists for 60 seconds (6 intervals, each lasting 10 seconds), indicating a more consistent issue.
Note: Remember, system triggers are pre-defined and cannot be edited. They can only be enabled or disabled according to your monitoring needs.
-
Build a Custom Trigger
You can build your own trigger from scratch, defining its Detail and Conditions (see Editing and Creating Triggers). You can also copy a default system trigger as a starting point, as described below.
Copy a Default System Trigger
CommandCTRL provides a set of default system triggers. Default system triggers cannot be edited directly — they can only be enabled or disabled. To customize one, copy it to create your own editable trigger, then disable the original system trigger so that only your version is active.
-
In the side navigation panel, go to Triggers.
-
Locate the default system trigger you want to base your trigger on.
-
Click the Copy icon in the trigger’s row to create an editable copy. (You can also open the trigger and click Copy This Trigger).
-
Edit the copied trigger’s Detail and Conditions as needed (see Editing and Creating Triggers), then save it.
-
Disable the original default system trigger so that only your copy is active (see Viewing and Customizing Triggers).
Additional trigger condition fields are available in 1.5, including Display Protocol metrics such as Display Protocol Frames Per Second, Display Protocol Packet Loss Uplink, Display Protocol UDP Latency, Display Protocol TCP Latency, and Display Protocol HDX Latency.
Trigger Highlighting in Real-Time and History
When a trigger’s conditions are met, CommandCTRL highlights the affected metric on the dashboard. Trigger highlighting appears in both Real-Time mode and History Playback mode, so you can see when a condition was met while reviewing a machine’s history.
Default System Triggers
CommandCTRL ships with the following default system triggers. Each monitors a metric over a number of intervals and fires when its condition is met:
|
Name |
Description |
Conditions |
|---|---|---|
| Disk average response time is high | Default trigger to monitor disk average response time | Disk Average Response Time is greater than 25 for 6 intervals |
| Ethernet latency is high | Default trigger to monitor ethernet latency | Ethernet Latency is greater than 250000000 for 6 intervals |
| Frame Quality is low | Default trigger to monitor frame quality | Display Protocol Frame Quality is less than 50 for 6 intervals |
| Frames/Sec is low | Default trigger to monitor frames per second | Display Protocol Frames Per Second is less than 10 for 6 intervals |
| Image Frames/Sec is low | Default trigger to monitor image frames per second | Display Protocol Image Encoded Frames Per Second is less than 10 for 6 intervals |
| Image quality is low | Default trigger to monitor image quality | Display Protocol Image Quality is less than 50 for 6 intervals |
| Latency high on Blast | Default trigger to monitor Blast latency | Display Protocol Blast Latency is greater than 250 for 6 intervals |
| Latency high on HDX | Default trigger to monitor HDX latency | Display Protocol HDX Latency is greater than 250 for 6 intervals |
| Latency high on PCoIP | Default trigger to monitor PCoIP latency | Display Protocol PCoIP Latency is greater than 250 for 6 intervals |
| Latency high on TCP RDP | Default trigger to monitor TCP latency | Display Protocol TCP Latency is greater than 250 for 6 intervals |
| Latency high on UDP RDP | Default trigger to monitor UDP latency | Display Protocol UDP Latency is greater than 250 for 6 intervals |
| Machine CPU usage is high | Default trigger to monitor machine CPU usage | CPU Utilization Percent is greater than 75 for 6 intervals |
| Machine GPU usage is high | Default trigger to monitor machine GPU usage | GPU Utilization Percent is greater than 75 for 6 intervals |
| Machine RAM usage is high | Default trigger to monitor machine RAM usage | Memory Utilization Percent is greater than 75 for 6 intervals |
| Packet loss is high | Default trigger to monitor packet loss | Display Protocol Packet Loss Uplink is greater than 50 for 6 intervals |
| Process CPU usage is high | Default trigger to monitor process CPU usage | Process CPU Percent is greater than 75 for 6 intervals |
| System battery level is low | Default trigger to monitor battery level | Battery Remaining Percentage is less than 25 for 6 intervals |
| Wi-Fi latency is high | Default trigger to monitor Wi-Fi latency | Wi-Fi Latency is greater than 250000000 for 6 intervals and Wi-Fi State is equal to 1 |
| Wi-Fi strength is low | Default trigger to monitor Wi-Fi strength | Wi-Fi Strength is less than or equal to 25 for 6 intervals and Wi-Fi State is equal to 1 |
