Monitoring Studio KM for PATROL

Release Notes for v9.1.00

Home  Previous  Next

What's New

Command Lines Analysis: It is now possible to execute a command locally on the PATROL Agent while monitoring a remote host.
Database Query Analysis: Oracle Exadata databases are now supported.
SNMP Polling: Monitoring Studio now supports SNMP v2c and SNMP v3.

Changes and Improvements

Files and Folders Remote Monitoring: The path of the file or folder to monitor can now contain environment variables.
Command Lines Analysis: Performance has been improved for remote Windows command lines analysis.
Monitoring Studio now supports AES 256 encryption.
The Export/Import Configuration features have been improved:
The Export Configuration was used to export an entire Monitoring Studio configuration or a single Group configuration. The former KM command has been split into two new KM commands: Backup Configuration (entire Monitoring Studio configuration) and Export Configuration (single Group configuration).
Host information, credentials, or Group Constants can now be cleared when exporting a Group configuration. This allows you to create a Monitoring Studio template which can then easily be tailored to the monitored system on which it will be imported by providing other credentials, or host information.
Debug Mode:
It is now possible to indicate the date and time at which the system must stop logging debug information.
Debug files are now automatically generated in the %PATROL_HOME%\log or $PATROL_HOME/log folder.
The product build number is now reported in the debug log file and displayed in the About window (KM Commands > About...).
The Collection Hub debug file now contains more detailed information about its operations.
The Collection Hub is now separated from other KMs. As a result, files are no longer shared with other KMs, thus preventing any compatibility issues.

Fixed Issues

Local Files Monitoring: Monitoring Studio failed to properly set the Exists parameter to ‘1’ for local files that were detected as ‘not present’ upon a collect.
Folders Monitoring on a localhost (UNIX or Linux): Monitoring Studio would sometimes report incorrect values for the Exists parameter and trigger false alerts.
Command Lines Analysis|Files and Folders Remote Monitoring: When an error occurred, the error message displayed in the annotation of the Status parameter was empty.
Command Lines Analysis: When a command line could not be executed on a remote host, the Result parameter displayed the name of a temporary file used by the Collection Hub instead of the actual command line's result.
SNMP Trap Listening: Monitoring Studio now properly handles SNMP Traps coming from an IP Address that equals to "".
The Multi-Parameter Formula feature now enables selecting parameters which PATROL IDs contain the semi-colon (;) character.
Database Query Analysis: In some cases, when performing a SQL query on a Microsoft SQL database, the connection to the Microsoft SQL server failed with the following error message: “Unable to get information from SQL Server:<hostname>”. The Microsoft SQL Driver has been updated to fix the connection error.
Dynamic String Searches: Column properties are now properly taken into account.
Group constants containing "PASSWORD" in their name are now properly decrypted.
Due to an issue with the BMC PATROL Central Operator – Microsoft Windows Edition console, most of the dialog boxes that displayed a "Please wait" message have been removed.
The Collection Hub no longer crashes when too many requests time out simultaneously.

Known Limitations

SNMP Trap Listening: SNMP v2c and SNMP v3 are not supported.
Dynamic String Searches | Dynamic Numeric Value Extractions: these monitors require a temporary file to collect information. The temporary file name is built from the monitor and monitor's parents ID. In some cases, the ID length can be superior to 256 characters making the temporary filename too long and preventing the collect of information. Although the way the filename is built has been improved in v9.1.00 to be shorter, this issue can still occur in rare cases. If you encounter this problem, shorten the ID has much as possible.