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. |
| • | Monitoring Studio now supports carriage returns in configuration variables when importing a PATROL classic configuration in a CMA policy. |
| • | Database Query Analysis: The default port number for Microsoft SQL Server is now 1433. |
| ▪ | 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. |
| ▪ | As TrueSight Presentation Server does not support Agent Actions, it is no longer possible to turn on and off the debug mode through the Agent Actions > Debug… menu command. |
| ▪ | The product build number is now reported in the debug log file. |
| ▪ | 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 attribute 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 attribute 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 attribute was empty. |
| • | SNMP Trap Listening: Monitoring Studio now properly handles SNMP Traps coming from a an IP Address that equals to "0.0.0.0". |
| • | 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. |
| • | Group constants: the constant value was converted to uppercase preventing all case sensitive Monitors (e.g., Command Lines, Files, Folders, etc.) from using it. |
| • | The Collection Hub no longer crashes when too many requests time out simultaneously. |
| • | Monitoring Studio would sometimes be unable to access the passwords saved in the secure store which would lead to connection issues. |
Known Limitations
| • | SNMP Trap Listening: SNMP v2c and SNMP v3 are not supported. |
|
