Rules are based on metrics. Metrics are measurements of a transaction. There are four basic metrics that are defined for all transactions:
Metric | Description |
---|---|
Performance | End-to-end response time of the transaction measured in seconds |
Availability | Number of availability errors in the transaction Availability errors occur when the application does not respond, or when the application responds with an error that indicates it is unavailable. The availability rate provides information regarding whether the application is running and whether it provides basic responsiveness to client requests. |
Accuracy | Number of accuracy errors in the transaction Accuracy rates are calculated with the assumption that monitored applications are working as designed and that the information transmitted to clients is correct. Functions that can be evaluated to determine accuracy include link checking, content validation, title validation, and response data verification. If a monitoring script contains customized functions that are used to ascertain system accuracy, those functions are factored into the accuracy rate as well. |
Execution | Number of execution errors in the transaction An execution error indicates that there were problems with the script execution. It does not indicate anything about the health of the application |
In addition to the basic metrics, page timers and custom timers that are defined in your scripts are measured, and you can define rules based on their measurements. Page timer and custom timer metrics are measured in seconds.
There are four default rules, that use the out-of-the-box metrics. These are automatically applied to all of your synthetic transactions. All of the default metric rules are active by default.
The following default metric rules are included out-of-the-box:
Default Rule | Description |
---|---|
Performance | Default values:
|
Availability | Default values:
|
Accuracy | Default values:
|
Execution | Default values:
|
*Critical thresholds are disabled by default
You can modify the thresholds, and notification settings of the default metric rules, or activate/deactivate them. You cannot delete default metric rules.
You can define additional rules for the predefined metrics to apply to specific applications. Each rule must apply to a unique combination of application, Execution Plan, transaction, metric and location.
For example, if you define a rule that measures performance for:
MyApp
MyEP
MyTran
Houston
You cannot define another performance rule for the same combination of MyApp
, MyEP
, MyTran, and Houston
.
Note
An Execution Plan must have run at least once before you can define metric rules for that Execution Plan or any of its transactions.
More general rules are overridden by more specific rules. For example, if you define a Performance rule for an application and for Any Execution Plan, it is applied to every Execution Plan for that application. If you then define another Performance rule for a specific Execution Plan of that application, the Execution Plan-specific rule is applied to that one Execution Plan, and the application-level rule is applied to all of the remaining Execution Plans for that application that do not have a rule of their own.
You can deactivate or activate any rules, including the default rules. Deactivating a rule means that no events are generated and no notifications are issued by the deactivated rule. If a rule is deactivated, and a more general rule covering the rule's metric is active, the more general rule takes effect.
Note
If you are editing default metric rules, only the Thresholds and Notifications and the Status can be modified.
When you edit metric rules, if there are open events for these rules, they will be closed if the changes make the events no longer relevant.
On the Create/Edit Synthetic Rule page, enter or modify the following details:
Field | Description | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Name (required) | Logical name for the metric rule. Metric rule names must be unique. Maximum length is 255 characters. | ||||||||||||||
Status | Active or Inactive If the status is set to Inactive, no events are generated and no notifications are sent. | ||||||||||||||
Application (required) | Application to which the rule is applied
| ||||||||||||||
Execution Plan | Execution Plan to which the rule is applied Note An Execution Plan must have run at least once in order for it to be available on this list. From the dropdown:
| ||||||||||||||
Transaction | Transaction to which the rule is applied From the dropdown:
| ||||||||||||||
Metric | Metric that the rule is based on Default value is Availability. From the dropdown, select a metric. The metrics available for selection are generated based on data from previous runs of the selected Execution Plan. This means that the Execution Plan must have run at least once for metrics to be available for selection. When you select a metric, the following details are displayed about the metric:
| ||||||||||||||
Thresholds and Notifications | Defines the thresholds that trigger events and notifications to be generated for the selected metric Default settings for thresholds are inherited from the Default metric rule of the same metric. For example, if you create a new Availability rule, the values for your new rule are initially set to the values you have defined in your default Availability rule. This is true even if the default rule is inactive. Timer metrics' use the default Performance rule's values as default values. To set or edit thresholds and notifications, do the following:
| ||||||||||||||
Location | Location to which the rule is applied From the dropdown
|
Click one of the following:
Save - saves the rule and leaves the page.
Clone of
prepended to it. You must modify the application, Execution Plan, transaction, metric, or location. You cannot save the rule with the same details.From the action menu for the rule you want to activate/deactivate, select Activate or Deactivate.
Note
If you deactivate a synthetic metric rule, all open events that were opened for the rule are closed.
From the action menu in the table title bar, select Activate Selected or Deactivate Selected.
Note
If you deactivate synthetic metric rules, all open events for the rules are closed.
From the action menu for the rule you want to clone, select Clone.
The Create Synthetic Metric Rule page opens with all of the fields populated with the same values as the rule you cloned except for the Name, which has Clone of
prepended to it. You must modify the application, Execution Plan, transaction, metric, or location. You cannot save the rule with the same details.
From the action menu for the rule you want to delete, select Delete.
Notes
The Delete option is not available for default rules.
If you delete a synthetic metric rule, all open events for the rule are closed
From the action menu in the table title bar, select Delete Selected.
Note
If you delete synthetic metric rules, all open events for the rules are closed.
The Synthetic Metric Rules list includes details about all of your defined metric rules, including the default rules.
Click any column heading to sort the table by that column.
Enter text in any of the filter boxes, to show only rules that include that text in the field filter.
The Synthetic Metric Rules list includes the following information:
Field | Description |
---|---|
Status | Indication of whether the metric rule is currently active If the status is set to Inactive , the metric rule is not applied to transaction results. Filtering by All shows both statuses. |
Name | Logical name of the synthetic metric rule |
Metric | What the metric rule is measuring
|
Application | The application to which this rule applies A rule can apply to a single application, or to Any application (for default rules only). |
Execution Plan | The Execution Plan to which this rule applies A rule can apply to a single Execution Plan, or to Any Execution Plan. |
Transaction | The transaction to which this rule applies A rule can apply to a single transaction, or to Any transaction. |
Location | The location to which this rule applies A rule can apply to a single location, or to Any location. |
Minor | The threshold for issuing a minor event The number in parentheses () indicates the number of consecutive executions of the transaction that must breach the threshold in order for an event to be issued. |
Critical | The threshold for issuing a critical event The number in parentheses () indicates the number of consecutive executions of the transaction that must breach the threshold in order for an event to be issued. |
Notification | Indication of whether a notification is issued Notification can have the following values:
Filtering by All shows rules with all notification types. |
If you do not want SLA-based events to be generated, you can disable them. To do this, from the TrueSight Operations Management menu, select Configuration > Synthetic Metric Rules and scroll down to the bottom of the page to the Synthetic SLA section, and click the SLA Events switch to turn it off. The switch effects all applications. If you have synthetic SLA events disabled, and you want to turn them on, you can use the same SLA Events switch. NotesEnabling and disabling synthetic SLA events
Synthetic metrics, rules, and events
Investigating application issues reported by synthetic health events
Analyzing synthetic health details
Editing an application's synthetic settings
Converting from Monitoring Policies to Synthetic Metric Rules
17 Comments
Yashwant Singh
Harihara Subramanian
Lisa Jahrsdoerfer
Harihara Subramanian
Alexandre Boyer
Benjie Wolicki
Harihara Subramanian
Diane Porter
Harihara Subramanian
Shira Avron
Harihara Subramanian
Benjie Wolicki
Harihara Subramanian
Avneesh Jain
What do you mean by consecutive here, it should be the next execution in which the error occurs and because of which it should generate an alert. Right ??
Correct me, if I am wrong here?
Harihara Subramanian
Benjie Wolicki
Hi Avneesh,
Consecutive here is the number of Executions one-after-the-other that violate the threshold. This would mean that if you enter 2, an event is generated only if two Executions, one-after-the-other, violate the threshold. If there is a good Execution between the violations, no event is generated.
Harihara Subramanian