10.7.00 enhancements

TrueSight App Visibility Manager 10.7.00 offers the following key features and enhancements:

Updated support for the App Visibility Manager

Updated operating system support for Real End User Experience Monitoring components

Corrected Real End User Experience Monitoring security vulnerabilities

The following enhancements to the App Visibility agent for .NET provide expanded data visualization for your .NET Framework applications. The features were added to version 10.5.00.001 (Fix Pack 1), and incorporated in this version.

• Standalone for WCF. You can now monitor standalone services that run on a supported version of .NET Framework and use Windows Communication Foundation (WCF). For more information, see Monitoring-standalone-services-for-NET-Framework.

• DateTime and GUID values. For .NET Framework applications, including standalone services, you can now see the DateTime and GUID values with the code-level transaction information. The values are displayed with the transaction trace details, as "Custom Information."
• Module name. You can now see the module name for methods with the code-level transaction information. The module name is displayed with the transaction trace details, as "Custom Information."
  
  For general information about code-level details, see Viewing-a-trace-at-the-code-level.

Synthetic metric rules

TrueSight Synthetic Monitor now includes metric rules for monitoring the metrics of synthetic executions. Events are generated by these rules.

• Thresholds defined for the rules are customizable on multiple levels:
  • Application
  • Location
  • Execution Plan
  • Transaction
  • Timers (TOM-7962)
• Rules can be defined to generate an event for a single breach of the defined threshold or for multiple consecutive breaches (TOM-12875, TOM-22878).
• Events generate notifications that are issued to the channels you have configured in your presentation server. Notifications include any relevant error messages, and can include customized notes or metadata (TOM-19377, TOM-22704).

For more details, see Managing-synthetic-metric-rules.

Synthetic Health view

The Synthetic Health view shows the current health and a 24-hour overview of your application based on its synthetic executions, and the metric rules defined for it. You can also view historical synthetic health data by selecting a different day. The Synthetic Health view is updated every minute. Data is displayed for all transactions as they run, and is not tied to any fixed intervals (TOM-14392, TOM-20390, TOM-24470). For more details, see Investigating-application-issues-reported-by-synthetic-health-events.

Synthetic Health Analysis view

The Synthetic Health Analysis view shows detailed synthetic health data for a single hour from the Synthetic Health view. The view can be filtered to show the health based on selected metrics, locations, Execution Plans, and transactions. The following tabs are included:

• Events - details about the events in the selected hour
• Graphs - a graph of the performance metrics, including all timers shown individually, in the selected hour (TOM-10818, TOM-20897)
• Executions - details of the executions that ran in the selected hour

For more details, see Analyzing-synthetic-health-details.

Synthetic metric reports view

Reports, based on the results of synthetic executions can be viewed in the user interface, or exported as PDFs or as raw data in a CSV file. Reports can be generated for a single day, a week, or a month (TOM-13611). For more details, see Viewing-synthetic-health-reports.

Reports also include comparisons to a parallel time period.

Synthetic Monitor - Show Recent Executions

In TrueSight Synthetic Monitor you can now see the results of the most recent executions of an Execution Plan directly from the Execution Plan settings. For more details, see To view the recent executions for an Execution Plan.

Deep-dive visualization for integrated products

You can integrate App Visibility Manager with Real End User Experience Monitoring Software Edition to access code-level diagnostics data about a transaction from a monitored browser session. For more information, see Integrating end-user experience monitoring with deep-dive application diagnostics.

Added support for on-screen reports

On-screen reports are now implemented using an HTML5 format. This means the reports are available on all browser versions.

Previously, viewing on-screen reports required support for the NPAPI plugin, which some browsers no longer support.

On-screen reports enable you to visualize performance statistics in the Real User Analyzer by using pre-configured and custom reports.

Changed on-screen reports

As part of this change to HTML based on-screen reports, there are some changes in the reports capabilities.

Some reports types included two Y axes. For example, the Report for Latency has two Y axes, "Latency (ms)" on the left side and for "Requests" on the right side.

In the old implementation, the user can zoom and scroll both axes independently and each zoom/scroll only changes the parts of the graph that correspond to the zoom/scroll action.

In new implementation, the user can zoom and scroll only using the axis on the right side of the report, and each zoom/scroll changes all the parts of the graph, not just the graph elements that correspond to the axis that the user performed the zoom/scroll action.

Added SNMP service support

BMC Real End User Experience Monitoring Software Edition can report information through SNMP to a managing system in your network.   

This passive end-user experience monitoring provides an SNMP MIB that enables your SNMP manager to get (read-only) management data from the end-user experience component, such as the following metrics:

• OS-level standard metrics such as CPU usage or disk usage
• Traffic-related metrics such as Watchpoint data from a Real User Analyzer

To set up REUEM as a managed system, you enable the service, configure a local SNMP agent, and then configure the SNMP MIB or SNMP traps. 

Added a Trace object extraction rule

For BMC Real End User Experience Monitoring Software Edition, added a new extraction rule to a Trace object custom field, you must use only the following Data Source field options after selecting the rule format type:

Title Checker in URLChecker script has improved handling for tab and space characters

The title verification in the Title Checker of the URLChecker script supplied by BMC includes improved handling for tab and space characters (TOM-22934).

Extended Execution Plan name

Execution Plan name now supports up to 256 characters (TOM-23015).

Reclassifying errors in Synthetic Monitor

You can now reclassify Execution errors and Accuracy errors as Availability errors in Synthetic Monitor (TOM-23305, TOM-25956). For more details, see Reclassifying-Synthetic-Monitor-Execution-errors-and-Accuracy-errors-as-Availability-errors.

Simplified execution log download

The process for downloading execution logs in TrueSight Synthetic Monitor has been simplified to remove unnecessary steps (TOM-13551).

Silk Performer script version numbering

Silk Performer version 17.5 now includes a Project Version field that is used in TrueSight Synthetic Monitor to track the version numbers of your scripts.

Corrected labels in TrueSight Synthetic Monitor

Labels used in the user interface were modified to more closely adhere to industry standards (TOM-24464).

Notes in TEA Agent configuration file

Notes in the TEA Agent configuration file were expanded to clearly identify parameters that should not be modified (TOM-24469).

Enhanced connection handling in App Visibility

Connection handling between App Visibility and the Presentation Server was enhanced to avoid stuck requests (TOM-28685).

Expanded Synthetic event payloads

The event payload for events in TrueSight Synthetic Monitor has been expanded to populate more event slots and include more data.

File type changed in execution logs

Execution logs for scripts created with Silk Performer version 17.5 generate .tlz files instead of .xlg files. Scripts that were created with previous versions of Silk Performer will continue to generate .xlg files. File contents and function are identical, and both are fully supported.