Configuring optional alert detector settings

There are several detector settings that you can modify for the alert to be triggered in very specific situations. These settings apply to the following user-defined alert types:

Specify which part of traffic you want to monitor with your alert

Select a dimension that you want to monitor

If you select a dimension, the thresholds that you define are applied to each dimension of a selected type (for example, each tier or software service). Also, in the alert notification message, you receive information about each selected dimension separately (a separate entry for each dimension).

If a dimension is not selected, the thresholds are applied to the aggregated metric values for all dimensions and the notification also contains aggregated information for all dimensions (one entry).

To select a dimension:

  1. Click Add iconAdd dimension to add a dimension selection box to the Monitored dimensions section.
  2. Move the pointer over the dimension name and click it to display a complete dimension list.
  3. Select a dimension from the list. For an explanation of all available dimensions, see Dimensions available for user-defined alert definitions.

Specify additional dimension filters

By defining filters, you narrow down the applicability of the alert to a specific dimension or to a range of dimensions. You can define filters for dimensions other than those selected in the Select a dimension that you want to monitor step., or even define filters if no dimension was selected.

To add a dimension filter:

  1. Click Add iconAdd filter to add a filter selection box to the Dimension filters section.
  2. Move the pointer over the dimension name to display a complete dimension list.
  3. Select a dimension from the list. For an explanation of all available dimensions, see Dimensions available for user-defined alert definitions.
  4. Define a filter expression. For information about filter syntax, see Filtering on text fields.

Specify the conditions under which the alert should be raised

Change the default comparison mode setting

A comparison mode describes how the metric value should be compared against threshold value. There are three modes to choose from: single (default), absolute, and relative.

In single mode, threshold conditions are compared to a metric value from the last monitoring interval. This is the default and is sufficient for most purposes.

For more information, see Comparison modes overview.

Only if baseline condition is selected - Select the baseline source

This setting specifies whether to use the average or pinned baselines for the baseline condition. By default, the average source is selected. This option is available only for generic performance, transaction performance, and Citrix performance alerts. It will not work unless the selected baseline type is enabled for that combination of metrics and dimensions.

Specify whether an additional alert should be raised if no traffic data is observed

Typical alerts are triggered by activity in data files located on the AMD. However, if no traffic data is observed or analyzed, and no data is sent to the report server, the alert cannot be triggered. The Treat no data as zero (0) option allows for that specific alert to be raised when no traffic data at all is observed for the monitored software service, server, or site.

Note:

  • If NAM becomes inoperative and no monitored traffic data is generated, the alert will not be raised because the performance alert processing is triggered by incoming new monitored traffic data.
  • Citrix performance alerts support the Treat no data as zero (0) option only for the Number of sessions and Number of active user sessions metrics.

For example, a software service is being monitored where a number of operations are expected to occur during every monitoring period. Under normal circumstances the data presented on the report would show data for the entire time range. If no data was received for that software service by the report server, the report would not reflect the missing monitoring period. The report would present analysis on incomplete data (the missing data sets would be unacknowledged).

By default, this option is disabled. To enable it, select the Treat no data as zero (0) check box.

Select an auxiliary metric

This is an optional parameter and is not compared with any thresholds. You select it from a predefined metric list or compose it from several metrics as described in Step 3. The value of this metric can be included in the alert message, so it can be used for supplying additional information to the alert recipient.

For example, if in Step 3 you defined an expression that calculates the percentage of slow operations in the total number of detected operations, you can select Operations as your auxiliary metric. This results in both the percentage of slow operations and the total number of operations being reported in the notification message. If the number of operations turns out to be very small, then even if the percentage of slow operations is substantial, the problem may not be serious even though the triggering conditions are met and the alert is raised.

An auxiliary metric can also be used when defining output filters for an alert. For more information, see Specifying output filters.

Configure output filters

On the Output filters tab, you can set additional conditions on alert output fields, so that only alerts satisfying these conditions are raised. For more information, see Specifying output filters.

Modify default alert propagation settings

Do this on the Propagation settings tab.

By default, an alert is raised after one interval in which the defined conditions are met and lowered after one interval during which the conditions are not fulfilled, but you can change this setting and also specify when the alert should be re-issued or canceled.

You can also define additional messages that are appended to the main notification message whenever a specific event occurs. For more information, see Modifying alert propagation settings.