Skip navigation
Share:|

One of the greatest challenges users face today is defining what is a problem versus what is normal behavior. Synthetic Metric Rules (SMRs) were introduced in TrueSight Synthetic 10.7. They are used to define how synthetic transactions are monitored. This powerful functionality allows users to create rules that are more granular than ever before. SMRs significantly change the user experience and monitoring capability provided with the synthetic monitoring solution.

 

As you know, Events break down into Rules (defining what is a problem versus normal behavior) and Conditions (what to do when a particular problem is detected). In TrueSight, it is primarily TSIM that handles Conditions (e.g. integration with Remedy to open tickets when a problem is detected). SMRs fall into the first category (event notification when there is a problem). SMRs are all about how granularly the user can define what is a problem versus what is normal behavior. In TrueSight Synthetic 10.5 and earlier, users had to rely on SLA metrics to define Rules. These SLA metrics are only aggregated over a 5-minute interval. The 5-minute interval is extremely limiting. Say, for example, you have a specific URL Checker script that pings a web page once per minute. Let's say there are 5 executions in a 5-minute interval. If those 5 executions take 1.1, 1.2, 1.1, 1.2, and 5 seconds respectively and you set the threshold to 2 seconds and 20%, the SLA would fire if any one transaction takes more than 2 seconds to complete. With SMRs you have very fine-grained control. You can create a rule that says 2 consecutive transactions must be over 2 seconds which provides a more accurate rule and thus fewer false-positive alerts resulting in earlier detection of the problem.

 

With TS Synthetic 10.7 and 11.0 we provide Synthetic Metric Rules and superior data visualization. This includes metric rules for monitoring of metrics of synthetic executions:

 

  • Synthetic Metric Rules
  • Synthetic Health view
  • Synthetic Health Analysis view
  • Synthetic metric reports view

 

Below are some screenshots and hyperlinks to the online documentation to give you a sneak peek and guide you through the world of SMRs:

 

1) On the Synthetic Metric Rules page you can define and manage these rules and the criteria for generating events and issue notifications.

 

Managing Synthetic Metric Rules

 

 

2) Synthetic Health view

 

Investigating application issues reported by synthetic health events - BMC TrueSight App Visibility Manager 11.0

 

 

3) Synthetic Health Analysis view

 

Analyzing Synthetic Health Details

 

 

4) Synthetic Health Reports

 

Viewing Synthetic Health Reports

Share:|

Have you heard about the latest changes with Synthetic End User Experience Management in 2.6.00 and 2.6.10 Service Pack 1? Here are just a few of the exciting changes in the latest releases. For the full list, take a peek our online documentation:

2.6 - Improvements to Session Overview and integration with BMC Synthetic End User Experience Monitoring plug-in

2.6 - Enhancements to synthetic transaction monitoring

2.6 SP1 - Support for multiple synthetic TEA Agents on the same computer

 

But here are some of the highlights in the latest releases:

 

1) Ease of configuration

We removed some of the configuration prerequisites. You no longer need to add the confidentiality rules on the Collector to allow the synthetic post parameters to go through to the Analyzer. This is now taken care of for you. We still recommend using the synthetic configuration pack, but if you prefer to add the configurations manually (rather than using the config pack) there are now fewer steps than before.

 

In the default synthetic Watchpoints we replaced the Watchpoint called "All synthetic transactions with errors" with "All synthetic transactions excluding timers." When using this Watchpoint with dashlets and reports you don't get the timer impact on the aggregations and the report is more accurate.

 

2) Ability to drill down into Synthetic Execution Logs from APM Console.
You can request an Execution Log from the APM Console by going to the Application Monitoring tab, select Performance Analysis >>  start analysis >> choose ”object”, mark synthetic & all data >> Request Execution Log File
All the Execution Logs that were previously uploaded to the APM Console are available on the Synthetic tab >> Execution Logs
Execution logs are actually packages containing all the files created during execution of the Execution Plan. This includes the TrueLog and the .wrt file and whatever else is created during the execution of an Execution Plan. This is important for drilling down and analyzing problems.

 

3) Availability, Accuracy and Execution error messages
With the previous release you could only see the number of Availability errors and number of Accuracy errors to get a general idea of the problem. With the latest release you now see the entire error message as reported during the execution.

 

4) Support for Silk Test scripts

You can now use Silk Test scripts with Synthetic EUEM. Before using a Silk Test script you need to give it a Silk Performer "wrapper" i.e. export the .stp file from Silk Test; then import into Silk Performer and make just a few customizations. See the section titled "To prepare a Silk Test package for the TEA Agent in our online documentation. For more details regarding configuring the Silk Test project with Silk Performer, see Borland's Silk Performer documentation.

 

5) TEA Agents can now run as a process

This is important for Silk Test, Citrix, SAP GUI scripts, etc. Previously you could only run TEA Agents as a service.

 

6) Ability to stop the TEA Agent from the console side, remotely

Previously you had to logon to the agent machine in order to stop the service.

 

7) Multiple Synthetic TEA Agents on the same computer
With SP1 you can now install more than one BMC Synthetic TEA Agent on the same machine.

 

 

 

Popular Knowledge Articles:

 

KA414631 - Where are the latest Synthetic EUEM files on the EPD?

KA416352 - TEA Agents are not running all of the transactions

KA414334 - Silk Performer Synthetic script not creating Watchpoint in Real User Monitor

KA415706 - Created simple URLChecker transaction but TEA Agent shows all transactions rejected

KA416166 - How does Synthetic EUEM performance compare to TMART?

KA416482 - Reached limit of 100 Incident Detection Rules

KA416483 - Maximum number of Watchpoints per Analyzer is 120

KA415439 - Can I install and run TEA Agents on the same machine as a TMART Execution Server?

KA416651 - The SEUEM Assisted MIGration Operations (AMIGO) program is designed to help you upgrade quickly, easily and safely

 

 

 

 

Feedback:

 

Help us determine how we are doing. Use the rating system at the bottom of this blog to rate this post! Feel free to comment as well. We want to hear from you!

Share:|

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

.

Filter Blog

By date:
By tag: