BMC strongly recommends configuring the BMC Synthetic End User Experience Monitoring system to increase the effectiveness of filters and the grouping of results. The recommended configuration provides following benefits:
This topic contains a description of the recommended settings for synthetic monitoring. Configure the system manually if you have a working system to which you want to add synthetic monitoring.
Note
Perform all configurations in the Real User Analyzer or Monitor. You can adjust the recommended or automatic configuration to suit you and your organization's requirements.
Define page Watchpoints (Administration > Watchpoint Management > Available Watchpoints) to enable detailed monitoring of the performance and availability for all synthetic transactions.
Watchpoints configuration for synthetic transactions
Watchpoint name | Type | Description | Traffic filter |
---|---|---|---|
All synthetic transactions | Page | Page Watchpoint to aggregate all synthetic transactions |
|
All synthetic transactions excluding timers | Page | All synthetic transactions, without showing custom timers and page timers. This Watchpoint is useful for dashlets and reports where timers might cause distortion. |
|
Add filters to the Watchpoint filter library (Administration > Watchpoint management > Filter library) to help further filter synthetic transactions.
Filter configuration for synthetic transactions
Filter name | Expression | Description |
---|---|---|
Synthetic all | (url.stem_string contains "bmc-synthetic-1.0" ignorecase) | Synthetic transactions, custom timers and page timers |
Synthetic timers | (url.stem_string contains "bmc-synthetic-1.0" ignorecase) AND (mime_type is "synthetic/timer") | Synthetic timers only |
Synthetic transactions | (url.stem_string contains "bmc-synthetic-1.0" ignorecase) AND (mime_type is "synthetic/transaction") | Synthetic transactions only (no timers) |
Create custom error-detection rules (Administration > Thresholds and problem detection > Error detection rules) to notify you about synthetic transactions with availability errors, accuracy errors, or execution errors.
Error-detection rule configuration for synthetic transactions
Match Policy | Severity | Category | Description | Filter Expression |
---|---|---|---|---|
Proceed | Error | Content (CT) | Synthetic transaction accuracy error |
|
Proceed | Error | Application (AP) | Synthetic transaction availability error |
|
Proceed | Error | Custom (CU) | Synthetic transaction execution error | (custom_synthetic_execution_errors > 0) |
Use the Move up and Move down arrows to ensure that the new rules appear before the first rule with a Stop match policy, as shown in the following image.
Example of the synthetic error-detection rules above the first Stop match policy
Click to enlarge image.
Create session termination rules (Administration > Data flow settings > Session detection, click Termination rules) to define the conditions under which the system considers a session ended. For synthetic monitoring, each run of an Execution Plan is a session.
Session termination rule configuration for synthetic transactions
Name | Filter | Termination Conditions |
---|---|---|
Synthetic termination rule |
| if inactive for 15 minutes or when a specific event occurs (Specify with filter expression) followed by 1 second(s) of inactivity |
Example of session termination rule
Click to enlarge image.
Add object custom fields (Administration > Data flow settings > Custom fields) and add an extraction rule to capture page data that you can later use in error-detection rules and other system entities. Create the following custom fields:
Page custom field and extraction rule configuration for Synthetic Accuracy Errors
Custom field | |
---|---|
Field name | Synthetic Accuracy Errors |
Description | Synthetic Accuracy Errors |
Grammar name | custom_synthetic_accuracy_errors |
Export name | x-custom-synthetic_accuracy_errors |
Expected data type | Integer |
Extraction rule for Synthetic Accuracy Errors | |
Traffic selection | |
Format | Filter expression only |
Extraction Name | Synthetic Accuracy Errors |
Filter Expression |
|
Data source | |
Source Field | POST parameter |
Key |
|
Transformation | |
Transformation | Use default value: None (use as is) |
Example of custom field and extraction rule for Synthetic Accuracy Errors
Click to enlarge image.
Page custom field and extraction rule configuration for Synthetic Availability Errors
Custom field | |
---|---|
Field name | Synthetic Availability Errors |
Description | Synthetic Availability Errors |
Grammar name |
|
Export name |
|
Expected data type | Integer |
Extraction rule for Synthetic Availability Errors | |
Traffic selection | |
Format | Filter expression only |
Extraction Name | Synthetic Availability Errors |
Filter Expression |
|
Data source | |
Source Field | POST parameter |
Key |
|
Transformation | |
Transformation | Use default value: None (use as is) |
Example of custom field and extraction rule for Synthetic Availability Errors
Click to enlarge image.
Page custom field and extraction rule configuration for Synthetic Execution Status
Custom field | |
---|---|
Field name | Synthetic Execution Errors |
Description | Synthetic Execution Errors |
Grammar name |
|
Export name |
|
Expected data type | Integer |
Extraction rule for Synthetic Execution Status | |
Traffic selection | |
Format | Filter expression only |
Extraction Name | Synthetic Execution Status |
Filter Expression |
|
Data source | |
Source Field | POST parameter |
Key |
|
Transformation | |
Transformation | Use default value: None (use as is) |
Example of custom field and extraction rule for Synthetic Execution Status
Click to enlarge image.
Add an extraction rule to custom fields (Administration > Data flow settings > Custom fields) to determine the POST parameter within a page that contributes its data to the field. Add rules to the following existing system custom fields:
Extraction rule configuration for Group ID field
Traffic selection | |
---|---|
Format | Filter expression only |
Extraction Name | Synthetic Group ID |
Filter Expression |
|
Data source | |
Source Field | POST parameter |
Key |
|
Transformation | |
Transformation | Use default value: None (use as is) |
Example of extraction rule for Group ID
Click to enlarge image.
Extraction rule configuration for User ID field
Traffic selection | |
---|---|
Format | Filter expression only |
Extraction Name | Synthetic User ID |
Filter Expression |
|
Data source | |
Source Field | POST parameter |
Key |
|
Transformation | |
Transformation | Use default value: None (use as is) |
Example of extraction rule for User ID
Click to enlarge image.
Extraction rule configuration for Application Name field
Traffic selection | |
---|---|
Format | Filter expression only |
Extraction Name | Synthetic Application Name |
Filter Expression |
|
Data source | |
Source Field | POST parameter |
Key |
|
Transformation | |
Transformation | Use default value: None (use as is) |
Example of extraction rule for Application Name
Click to enlarge image.
Extraction rule configuration for Page Name field
Traffic selection | |
---|---|
Format | Filter expression only |
Extraction Name | Synthetic Page Name |
Filter Expression |
|
Data source | |
Source Field | POST parameter |
Key |
|
Transformation | |
Transformation | Use default value: None (use as is) |
Example of extraction rule for Page Name
Click to enlarge image.
Synthetic transaction configuration workflow
Implementing Synthetic Device Configuration Pack
Monitoring synthetic transactions to predict application health and user experience