Share This:

What is the best practice for creating Synthetic Watchpoints?

 

Recommendation:

BMC strongly recommends implementing the Synthetic Device Configuration Pack so you can more quickly realize value from your monitored synthetic transactions. Implement the configuration pack on a new installation of the Real User Analyzer or Real User Monitor.

WARNING!

Do not implement the configuration pack on a system that already has manual configurations as the configuration pack resets all existing configuration to the default settings

 

If you want to implement the device configuration pack on a system that has manual configurations, be sure to back up your current configuration:

·        Select the Administration tab. From Manage Configuration, select Download device configuration.

·        Enter a passphrase. If you want to recover the backup configuration, you will need to reenter this passphrase.

 

If you prefer not to use the device configuration pack you will need to do these 5 steps manually on the Analyzer.

 

1)   After implementing the synthetic device configuration pack you will see two new page watchpoints:

watchpoints-for-synthetic-transactions.png

 

2)   After implementing the synthetic device configuration pack you will have three new custom error detection rules to notify you about synthetic transactions with availability errors, accuracy errors, or execution errors:

custom-error-detection-rules.png

3)   After implementing the synthetic device configuration pack you will have a session termination rule 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.png

4)   After implementing the synthetic device configuration pack you will have rules added to the following existing system custom fields: Group ID, User ID, Application Name

 

5)   After implementing the synthetic device configuration pack you will see an object-type detection rule. This defines synthetic objects as document-type objects.

object-type-detection.png

And this is how Watchpoints appear in the Analyzer after implementing the device config pack (or implementing the steps manually):

watchpointSummary.png

 

UPDATE!  With version 2.6.10, no synthetic configuration is required for the Collector.

 

After implementing the configuration pack and adding the Confidentiality policy, you can edit and add Watchpoints. Synthetic (as opposed to real) watchpoints are primarily based on POST parameters describing different Synthetic aspects.

 

In Synthetic EUEM you have pages and you have objects. With Synthetic there is one object for each page. It is a one-to-one relationship. You have one object and one page for each synthetic transaction execution.

 

With Synthetic EUEM there are more things you can do with pages than with objects. So for Synthetic, if you create watchpoints you should create watchpoints on pages.

 

The table below lists a few of the many queries available to you. This is not a complete list. It includes only queries most likely to be used. The rows shaded green are the most popular.

 

KEY

DESCRIPTION

EXAMPLE VALUE

bmc_syn_tea_id

ID of the executing agent

1

bmc_syn_tea_name

Name of the executing agent

SH

bmc_syn_tea_group_id

ID of agent group of this agent

1

bmc_syn_tea_group

Name of agent group of this agent

SH_LT

bmc_syn_bs_id

ID of executed Business Service

1

bmc_syn_bs

Name of executed Business Service

CheckMe

bmc_syn_ep_id

ID executed Execution plan

101

bmc_syn_ep

Name of executed Execution plan

CheckMeEveryFive

bmc_syn_tn_id

ID of the script used

1

bmc_syn_tn

Name of the script used

UrlCheck

bmc_syn_script

Name of the script used

UrlCheck

bmc_syn_av_err

# of Availability errors

0

bmc_syn_acc_err

# of Accuracy errors

0

bmc_syn_exec_err

# of Execution errors

0

bmc_syn_session_termination

Did the session terminate

false

.