11.3.01 enhancements

TrueSight Operations Management version 11.3.01 provides the following enhancements and changes:

The following sections provide information about the added and discontinued operating systems. For more information, see System requirements and compatibility.

Added support for operating system

TrueSight Infrastructure Management

TrueSight Presentation Server

App Visibility Manger server

App Visibility Manager Server components now support the following operating systems:

• Red Hat Enterprise Linux (64-bit versions): 6.9 and 7.4

• SUSE Linux Enterprise Server (64-bit version): 12 SP3

TrueSight Operations Management Reporting

See System requirements for more information.

Discontinued operating systems for TrueSight Operations Management Reporting

See System requirements for more information.

TrueSight IT Data Analytics

Discontinued support for operating system

TrueSight Infrastructure Management

TrueSight Presentation Server

App Visibility Manager server

App Visibility Manager Server components no longer support the following operating systems:

• Red Hat Enterprise Linux (64-bit versions): 6.6, 6.7, 7.0, and 7.1

• SUSE Linux Enterprise Server (64-bit versions): 12.0

App Visibility Manager Server no longer supports the following versions of App Visibility agent for Java:

• Oracle WebLogic Server 12c: Oracle 1.6
• Apache Tomcat 7.x: Oracle 1.6

Application server and App Visibility agent for Java version support

App Visibility Manager Server no longer supports the following application servers:

• IBM WebSphere Application Server (Full Profile) 7.0.x
• IBM WebSphere Application Server (Full Profile) 8.0.x
• Oracle WebLogic Server 10gR3
• Oracle WebLogic Server 11g

App Visibility Manager Server no longer supports the following versions of App Visibility agent for Java:

• Oracle WebLogic Server 12c: Oracle 1.6
• Apache Tomcat 7.x: Oracle 1.6

TrueSight Operations Management Reporting

See System requirements for more information.

TrueSight IT Data Analytics

You can use TrueSight Smart Reporting to generate reports with a simple drag-and-drop action. Smart Reporting uses TrueSight Operations Management Reporting as its platform to administer, compile, and publish reports, and uses Oracle or SQL Server as the application database.  The Report Engine is a Java application that collects event, impact, and performance data from TrueSight Infrastructure Management Server. , and compiles the data. The Report Engine periodically summarizes performance data, and calculates impact metrics using the events data.

TrueSight Smart Reporting integrates TrueSight Operations Management with Yellowfin, a third-party business intelligence and reporting tool. For information about Yellowfin, see the  Yellowfin documentation  (http://wiki.yellowfin.bi/display/USER74/Home).

For information about using TrueSight Smart Reporting, see the  TrueSight Smart Reporting documentation .

Enhanced synthetic metric rules and synthetic health analysis

• Multiple metrics: You can define metric rules to generate a single event if multiple metric thresholds are breached. You can define the event to be generated only if all of the thresholds are breached or if any of the thresholds are breached; in either case only generating a single event. (DRTSO-28854, DRTSO-36145)
• Violation frequency: New definition of the frequency of violations occurring helps you control the number of events that open. (DRTSO-28828)
• Multiple locations: You can define metric rules for a percentage of locations, or multiple specific locations. (DRTSO-28853, DRTSO-33966, DRTSO-36562)
• Notification email: You can define email addresses per synthetic metric rule either overriding the global email notifications that apply to all other applications or in addition to them. (DRTSO-28851, DRTSO-28852)

For details, see Configuring and managing synthetic metric rules.

You can analyze the synthetic health of your transactions and drill down to investigate issues in locations and the violations that contribute to specific events. For details, see Investigating application issues reported by synthetic health events.

New end-user experience monitoring dashlets

Enhanced monitoring capabilities for the App Visibility proxy enable expanded data collection for end user experience monitoring. The new infrastructure provides a high-availability environment for the proxy and historical data.

You can now collect end user experience information for several different page navigation elements so that you can better understand the end user experience and pinpoint issues for faster resolution. The following end-user experience dashlets are available:

• End User Experience Overview: Displays an overview of metrics that influence the end-user experience.
  For details, see End User Overview dashlet .

• End User Experience Metrics: Displays the performance impact and frequency of a variety of end user metrics and attributes.
  For details, see End User Experience Metrics dashlet .

The enhanced End User Experience Metrics dashlet replaces the Application Client Breakdown dashlet, which is no longer available.

Added support for tracing asynchronous technologies

Asynchronous transactions method is now supported with TrueSight App Visibility Manager.

The  product's code level view enables you to pinpoint the code behind the recorded instance. App Visibility drills down to the code of the trace.

When you view the code level for a trace, you can now see the parts of the trace that use asynchronous technologies in the tree or table view. The supported asynchronous technologies includes the .NET framework Task-based Asynchronous Pattern (TAP) and Java JDK executors.

For more information, see Viewing a trace at the code level.

You can now generate monthly consumption-based license usage reports that display the average reports of the following components:

• Third-party events
• Data streams
• Cloud streams
• Sentry streams

For more information, see Viewing and exporting the License Usage - Consumption Data report.

Activate or deactivate data collection at the PATROL Agent by configuring filters in a monitoring policy

For more information, see  Defining a monitoring policy.

New parameters for the API that lists details of all the policies

New operator for selecting Agents while creating a policy

While creating a policy, you can now use the in list operator for selecting Agents. The value of the in list operator can be a comma-separated list of Agent host names. 

For more information, see  Defining a monitoring policy.

App Visibility notification channels in the TrueSight console

Notification channels for App Visibility events and Synthetic Monitor events can now be defined in the TrueSight console. The following channels are available:

• Email
• Syslog
• SNMP

See Managing App Visibility notification channels for more details.

TrueSight Synthetic Monitor execution log retention

For every synthetic Execution Plan, you now have the option to set how the execution logs are saved. By default, execution logs are saved only for executions that encounter errors. This default option is implemented on existing Execution Plans for upgraded systems as well. See Editing an application's synthetic settings for more details. (DRTSO-13560)

TrueSight Synthetic Monitor fault tolerance for intermittent script errors

Intermittent script errors (7, 65, and 83, for error facility 71 - Browser Engine), which are usually caused by temporary conflicts between the script and local system environmental factors, are now handled differently. If one of these errors is encountered, the script is retried (three times). If one of the retries is successful, no error is recorded. If the errors persist, they are classified as execution errors.

Health event status of App Visibility components and Synthetic Tea Agents

Enhanced installation documentation

Added certificate troubleshooting documentation

Newly-added certificate troubleshooting documentation helps you resolve some of the problems that you may face while creating and importing signed certificates for the TrueSight Operations Management components. For more information, see Troubleshooting security certificate issues.