2.5.00 enhancements

This section contains information about enhancements in version 2.5.00 of BMC PATROL for IT Data Analytics.

Data collection enhancements

Version 2.5.00 of BMC TrueSight IT Data Analytics introduces the following new capabilities that are supported with Collection Agents 2.5:

• Default data patterns for collecting JSON data.
• New data collector, named Receive over HTTP/HTTPS, that can be used for receiving data over an HTTP/HTTPS protocol.
• Capability of specifying wildcard characters in the directory path for performing partial matches of directory names in the Monitor file on Collection Agent data collector.

For more information, see the following links:

• Assigning a data pattern for collecting JSON data
• Receive over HTTP/HTTPS data collector  
• Using wildcards in teh directory path

Central Monitoring Administration transformation

The Central Monitoring Administration console is discontinued. All the monitoring administration features are now available from the TrueSight console with enhanced functionalities, such as easier search and filtering options. For a quick understanding of this change, see Using wildcards in teh directory path .

With this change, you can install BMC PATROL for IT Data Analytics and configure Collection Agents by using the TrueSight console version 2.5. For more information, see the following links:

• Installing using TrueSight console
• Configuring using TrueSight console

Other improvements

With this release, the following improvements are available:

• The following problems are fixed.
  •  When the Central Monitoring Administration policy was disabled, the Java process related to BMC PATROL for IT Data Analytics did not stop automatically.
  • If too many Collection Agents started simultaneously and tried to connect with the same Collection Station, then these Collection Agents displayed a red status on the Administration > Hosts page of IT Data Analytics.
• Burst performance is improved when a bulk of Collection Agents try to connect with a Collection Station. 

In addition, while performing a monitoring configuration, the way of specifying the collection profile name has changed. While specifying a collection profile name that is imported via a content pack, the collection profile name must be specified in the format, "<collectionProfileName> [contentPackName>]".

Related topic

Known and corrected issues