11.3.03: Service Pack

Integration with Proactive Service Resolution

With Proactive Service Resolution (PSR), you can now integrate event management and incident management. This helps you to proactively manage the IT infrastructure risks that can impact the performance of your applications and services. For more information, see Integrating with Proactive Service Resolution to integrate event management and incident management.

Role-based access controls for shared dashboards

• You can now view, create, modify, delete, or share dashboards only if the tenant administrator provides the permissions in the authorization profiles. The relevant roles must also have permissions to view and manage dashboards. However, all shared dashboards from earlier versions are visible under the Shared Dashboards tab and a tenant administrator can restrict these permissions.
• Tenant administrators now have access to all the non-shared dashboards. This capability helps tenant administrators to manage dashboards that are no longer in use.
• You can now refresh the list of dashboards and search for dashboards.

For more information, see the following links: 

• Sharing and copying dashboards

• Adding and modifying dashboards

Orchestration policies for context-based event selection

You can now create an Orchestration policy and enable an Orchestration action that runs automatically to perform the triage and remediation actions when a relevant event occurs. You can also configure the event selection criteria in the policy to determine the type of events on which an Orchestration action must be enabled. 

Out-of-the-box Orchestration policies are now available for starting various types of services and cleaning up disk space.

For more information, see Managing Orchestration policies.

TrueSight Health Check Tool for optimizing your environment

The TrueSight Health Check Tool is now available to check if your environment is optimized for performance and stability. Use the recommendations from the generated report to reconfigure your system. For more information, see TrueSight Health Check Tool.

Meta tag filters to group cloud resources

You can now use meta tag filters in rule-based groups to organize cloud resources in various ways, such as their purpose, geographical association, name, and type. The meta tag filters enable you to search or filter cloud resources in TrueSight Operations Management. 

For more information, see Using meta tags to group cloud resources.

Ability to update the monitoring solution version

With version 11.3.03, you can change the monitoring solution version to the latest version while editing a monitoring policy.

For more information, see Defining a monitoring policy.

Regulate new incoming monitor instances

The addition of new PATROL Agents and Integration Services is blocked when the monitored instance count reaches the configured maximum limit. The new incoming instances are automatically queued in the INSTANCE_WAIT_LIST database table. When you reduce the instance count below the maximum limit, the queued instances are added to the Infrastructure Management server. For recommendations to reduce the number of instances, see Configuring Infrastructure Management self-monitoring .

SAP SQL Anywhere upgrade

When you upgrade TrueSight Infrastructure Management to version 11.3.03, the SAP SQL Anywhere (Sybase) database is upgraded from version 16 to 17. For more information, see Preparing to apply feature packs or fix packs on Infrastructure Management.

Support for Oracle 19.3

For Oracle 19.3.0.0.0, BMC has done only a limited testing with the standalone and HA environments. For more information, see Supported databases and Web consoles requirements for Infrastructure Management.

Automatic node status checks in a high-availability deployment

In a high-availability deployment of TrueSight Infrastructure Management, the pw system start command now automatically runs node status checks to ensure that the nodes are restarted in the correct sequence. For more information, see pw system start.

New event to indicate the out-of-sync status for cell databases

An internal event is now generated to indicate that the cell databases are not synchronized in an application high-availability deployment of TrueSight Infrastructure Management. For more information, see Configuring a cell to generate an out-of-sync event.

Availability of TrueSight Infrastructure Management

In a high-availability deployment of TrueSight Infrastructure Management, if any of the critical server processes become unavailable, the secondary node is now restarted instead of being shut down. This ensures the availability of the TrueSight Infrastructure Management server. For more information, see Error ID 101457 at Infrastructure Management Server messages.

Enhancements to handle a lost connection to the database

If connectivity to the database is lost and cannot be reestablished within 15 min, the TrueSight Infrastructure Management server (both servers in a high-availability deployment) is shut down to prevent data inconsistencies. For more information, see Reestablishing a lost connection to the database.

Serverless license support

With the serverless license, you can now monitor, view, and export the Serverless Streams - Details Report. This license enables you to monitor containers, such as Docker and Kubernetes, and other cloud computing services that do not require access to underlying hardware assets, such as servers or VMs.

Cloud VMs such as Amazon EC2 and Microsoft Azure are not included in the serverless license.

For more information about the report, see Consumption Data reports.

Short-term instances group

You can now clean up the devices and monitoring instances marked for deletion from the system within a short period. You can do this by configuring the new out-of-the-box System: Short-Term Instances group. By default the short-term period is set to 48 hours. You can change this value using the command-line option.

For more information, see Editing the system short-term instances group.

Automatic pruning of the nohup.out file

TrueSight Infrastructure Management 11.3.03 introduces automatic log pruning for the nohup.out file on Linux. You can also customize the pruning parameters.

For more information, see Customizing log pruning parameters for the nohup.out file on Linux.

CLI utilities to list and delete instances marked for deletion

You can now list the PATROL Agent details by running the pw patrolagent list command and delete instances marked for deletion in PATROL Agents by running the pw mfdinst command. For more information, see pw patrolagent list and pw mfdinst.

Renamed Single Metric Analysis options

You can now view the following changes on the TrueSight console when you select Single Metric Analysis from Monitoring Details > Performance Overview > Metric Comparison >  Edit Settings. There is no feature or functionality impact due to this change.

• The PATROL Agent Data column is renamed to PATROL Agent.
• The Obtain Data from PATROL Agent option is renamed to Obtain Data.
• The PATROL Agent option from the Thresholds column is moved to the PATROL Agent column and is renamed to Show Thresholds.
  
  

For more information, see Viewing monitor information in the TrueSight console.

Customizing the date format for Synthetic Metric Rules event notification

You can now customize the start and close date formats for Synthetic Metric Rules event notifications by using the portal property settings. The customized date format is applied uniformly to all supported languages. For more information, see Managing App Visibility notification channels.

Increased performance threshold limit for Synthetic Metric Rules

The performance threshold limit is now increased to 86400 seconds (24 hours) for minor and critical thresholds in Synthetic Metric Rules.

Improved audit trail log

You can now identify the user who enabled or disabled a synthetic application or execution plan from the <Presentation_Server_Install directory>\BMC Software\TrueSightPServer\truesightpserver\logs\App-Visibility.log file. For example, you can see log messages, such as:

• AV.SYN Application 'app1' was deactivated by user <username@orgname>. All associated execution plans are also deactivated.
• AV.SYN Execution Plan 'app1EP' in the 'app1' application was activated by user <username@orgname>.