Monitoring Studio KM for PATROL
Release Notes for v9.3.00
•PSL Commands Analysis: Monitoring Studio now supports PSL commands. The PSL Command Monitor makes it possible to execute PSL commands and analyze their result.
•Windows Event monitoring now supports regular expressions for selecting and acknowledging specific event messages.
▪supports the following new functions: swTableJoin(), swGetMaximum(), swGetMinimum(), swGetAverage().
▪it is now possible to create a String Search, Numeric Value Extraction, Text Pre-Processing, or Dynamic Object Builder for this Monitor.
▪the Result parameter was added to the SEN_MS_FORMULA application class to display the returned output of the formula.
•SNMP Browser: Monitoring Studio now supports SNMP v2c and SNMP v3 in the SNMP Browser wizard.
•JSON Support: The Text Pre-Processing Monitor now provides two new options to convert JSON output to CSV or flat map formats.
•The Web Request Analysis Monitor now uses a java-based engine to improve performance and flexibility.
•Credentials Management: It is now possible to improve credentials security by preventing password reuse.
•The Proxy Settings KM command was added to the SEN_MS_MAIN application class to let you configure shared proxy server credentials to be used to execute Web requests.
•The DiscoveryStatus and DiscoveryTime parameters were added to the SEN_MS_MAIN application class to report on the global discovery.
Changes and Improvements
•Folders and Command Lines: remote monitoring is now fully supported on Windows 2003.
•Web Requests (POST - Web Service): Environment variables can now be used when specifying the path to the 'Web Service Body'.
•Multi-Parameter Formula: All timeout and formula syntax errors are now identified and reported to the annotation of the Group’s CollectionErrorCount parameter with a more descriptive error message.
•Text Pre-Processing: It is now possible to filter the content of the Result parameter of a Monitor before parsing it to discard unwanted or unsupported text. The wizard provides new filter to keep specific lines or to keep/exclude lines matching a specific regular expression.
•Monitoring Studio's overall performance and responsiveness have been greatly improved to better handle large configurations.
•Using invalid Java credentials prevents data collection. The message displayed in the annotation of the CollectionErrorCount parameter and in the KM debug file now clearly identifies this Java settings problem.
•Monitoring Studio now prevents new groups to be created and removes all existing group instances when no compatible JRE is detected.
•To avoid potential authentication failures, Monitoring Studio prevents users from selecting or specifying SSH private key-based credentials for Monitors such as WBEM Query, Web Request, or Database Query which do not support this functionality.
•The folder where temporary files are stored is now emptied during the initial discovery cycle and temporary files are deleted at the end of each collection cycle.
•Group constants were replaced by their actual value in the Alert Actions wizard.
•When performing a String Search on log files with the Report matching lines: in the current collect only option selected, the LastMatchingLines parameter now only displays the last 50 matching lines found in the last collection.
•On rare occasions, WBEM queries could fail with Java 8.
•Alert actions set at the Nagios Performance Monitor level were not executed. They can now be set at the Nagios Plugin Monitor level only.
•When upgrading from Monitoring Studio v9.0.00 or v9.1.00, credentials and alert actions could be lost or corrupted leading to false alerts.
•Text Pre-Processing: false alerts could be triggered when searching for lines not containing a specific string.