|
What's New
| • | Wild characters (‘*’ and ‘?’) can now be provided in the file path when monitoring a file |
| • | To avoid the 140 characters limitation for text boxes in BMC Portal, the SQL query can be stored in a file on the RSM and executed using the %{FromRSM:filename} macro in SQL query Objects |
Fixed Issues
| • | When the file path contained either * or ?, the Performance Manager failed to retrieve the most recently modified file corresponding to the specified mask |
| • | String Searches and Numeric Value Extraction failed to handle empty content |
| • | When executing remote commands on Windows systems with non-English regional settings (or similar) the Performance Manager failed to evaluate the execution time |
| • | HTTP Post requests failed when performed through a Web proxy |
| • | The Performance Manager did not take into account the specified column number for numeric value extraction objects |
| • | The rescale factor in Numeric Value Extraction objects was not properly taken into account |
| • | The scientific notation was not properly handled by Numeric Value Extraction objects |
| • | One-row SNMP tables were not properly handled |
Changes and Improvements
| • | The parameters Count(HB) and Count(LB) of String Search objects are set to “No Data” when the parsed content is empty |
| • | A retry mechanism has been implemented to better handle flaky SSH connectivity and avoid false alerts |
| • | Added an option to specify the WMI impersonation level for command line execution on Windows systems. This allows the execution of commands that access another system remotely (the RSM launches a command on remote System A which accesses remote System B) |
|
