Converting from Monitoring Policies to Synthetic Metric Rules
Starting with version 10.7 of TrueSight Synthetic Monitor, transaction-based events can be generated using synthetic metric rules (see Synthetic metrics, rules, and events for more details). In earlier versions of TrueSight Synthetic Monitor, transaction-based events were generated only using agent thresholds defined in monitoring policies in TrueSight Infrastructure Management, and run using PATROL for Application Management. Use the information included here to convert your agent thresholds to synthetic metric rules. See Managing synthetic metric rules for details on defining synthetic metric rules.
To open agent threshold configuration in the TrueSight Console
To open agent threshold configuration in Central Monitoring Administration
From the Central Monitoring Administration menu, select Policies > Monitoring.
Select the policy for application management, and click the Edit
icon.Select Agent Threshold Configuration. When Agent Threshold Configuration changes to a link, click on it.
To open synthetic metric rule configuration
The following examples show the user interfaces of agent threshold configuration in the TrueSight Console and synthetic metric rule configuration as references.
Note
Examples shown here for TrueSight Infrastructure Management are for the Presentation Server. Where interface labels differ in Central Monitoring Administration, they are included in parentheses.
Agent Threshold Configuration and Synthetic Metric Rule Configuration
Use this table to map your agent threshold configurations to synthetic metric rule configurations.
Notes
- Agent threshold configuration includes elements that are not relevant for TrueSight Synthetic Monitor. Elements that are not relevant for TrueSight Synthetic Monitor are not described here.
- For best viewing, press F on your keyboard to use the full screen option.
| Agent Threshold | Metric Rule | |||
|---|---|---|---|---|
 | Monitoring Solution The value for this field is always Application Management. | NA | ||
 | Monitor Type Relevant values are: | Metric |  | |
 |
| Select the relevant custom timer from the Metric field. |  | |
| Select the relevant page timer from the Metric field. | |||
| Map to the appropriate Metric. See  Monitor Attribute. | |||
 | Scope Values are: | Application, Execution Plan, Transaction, and Location. |
| |
 |
| Modify the thresholds in the predefined global rule for the selected metric. | ||
| Identify the object the SID is pointing to and select the appropriate Application, Execution Plan, Transaction, and Location. Note Where Asterisks (*) appear in the SID as wildcards, use Any in the appropriate fields. | |||
| Monitor Attribute Values are: | Metric | | |
 |
| Accuracy | | |
| Availability | |||
| Execution | |||
| If the AM Synthetic Transaction monitor type is selected, map this to Performance. If AM Synthetic Custom Timer or AM Synthetic Page Timer is selected, map this to the specific page timer or custom timer. | |||
 | Threshold 1 / Threshold 2 (Alarm 1 / Alarm 2) | Minor / Critical Note If your agent threshold includes includes a Border Threshold, consider mapping the Max value to the Critical value in your synthetic metric rule. |   | |
 |
| Enter the value in the appropriate field for Minor or Critical. Response Time attributes in agent thresholds are measured in milliseconds. Performance metrics in synthetic metric rules are measured in seconds. Fractional values are allowed in metric rules, so you can accurately convert your values. For example, if you have a value of 500 milliseconds in your defined agent threshold, enter .5 seconds in synthetic metric rules. | | |
 |
| |||
 |
| Minor | | |
| Critical | | ||
 |
| Notification Threshold breaches always trigger events. You can select the following options for Notification:
|
| |
 |
| Set Consecutive to 1. |  | |
| Set Consecutive to the value of N. |
Comments
Log in or register to comment.