What's New
| • | Full support of PATROL Agent v9.0.00 and higher. |
| • | Database queries can now be performed natively on PostgreSQL databases with the Database Query Analysis tool. The connection method to be used is either the command line utility or the Java Database Connectivity. |
| • | JMX Monitoring: The JMX Monitoring tool now supports the following MBean application servers: |
| ▪ | JBoss 5.x, 6.x, and 7.x (EAP 6.x). |
| • | The following new macros can be used in Alert Actions: |
| ▪ | % {SW_USERNAME}: Username configured for the instance that triggered the alert. |
| ▪ | % {SW_PASSWORD}: Password associated to the username configured for the instance that triggered the alarm. |
| ▪ | % {BORDER_TYPE}: Border alert type of the parameter triggering the alert (OK, WARN, ALARM). |
| ▪ | % {BORDER_MIN}: Border minimum range of the parameter triggering the alert. |
| ▪ | % {BORDER_MAX}: Border maximum range of the parameter triggering the alert. |
| ▪ | % {BORDER_NTIMES}: Number of consecutive times the parameter triggering the alert must have a value outside the border range before the alert occurs. |
| ▪ | % {ALARM1_TYPE}: Alarm1 alert type of the parameter triggering the alert (OK, WARN, ALARM). |
| ▪ | % {ALARM1_MIN}: Alarm1 minimum range of the parameter triggering the alert. |
| ▪ | % {ALARM1_MAX}: Alarm1 maximum range of the parameter triggering the alert. |
| ▪ | % {ALARM1_NTIMES}: Number of consecutive times the parameter triggering the alert must have a value within the alarm1 range before the alert occurs. |
| ▪ | % {ALARM2_TYPE}: Alarm2 alert type of the parameter triggering the alert (OK, WARN, ALARM). |
| ▪ | % {ALARM2_MIN}: Alarm2 minimum range of the parameter triggering the alert. |
| ▪ | % {ALARM2_MAX}: Alarm2 maximum range of the parameter triggering the alert. |
| ▪ | % {ALARM2_NTIMES}: Number of consecutive times the parameter triggering the alert must have a value within the alarm2 range before the alert occurs. |
| ▪ | BPPM Integration: It is now possible to indicate the device the instances will be attached to in the BMC ProactiveNet console. |
| • | I2D Device Mapping can now be disabled by setting the /MASAI/SENTRY8/disableI2D configuration variable to 1. |
Changes and Improvements
| • | Alerts: Both encrypted and unencrypted application constants can be used in Alert Actions. |
| • | File Monitoring: A username and password can now be specified to monitor a file instead of using the PATROL default account. |
| • | Process Monitoring: The characters '-', '_', '.' can now be used when specifying a process username. |
| • | String Search: Date and time information can now be inserted in the regular expression(s) to be searched. Values are interpreted at run time. |
| • | Database Queries: Encrypted connections (SSL) with MS-SQL Servers are now supported by the Java connection method. |
Fixed Issues
Alerts
| • | SWSY-310 - No Alert Action was triggered when border thresholds were breached. |
| • | P1355 - The acknowledge alerts function did not work for file security monitoring. Attempting to acknowledge a file security monitoring alert triggered for the "Integrity" parameter instead caused the following popup message to appear "No file matches the entered mask. Cannot Acknowledge and update the security settings. |
Database Queries
| • | SWSY-189 - Authentication errors occurred when performing a SQL query on a MySQL database running on Windows. The password was not properly formatted when using the command line method to perform a SQL query on a MySQL database. Therefore most database queries did not work due to authentication failure. |
| • | P1230 - Instances were created but remained OFFLINE and no collect was performed when running a Database Query using the ODBC method. |
| • | P1354 - Errors related to updateable cursors were returned when performing queries against PostgreSQL databases when using the ODBC method. |
File Monitoring
| • | SWSY-358 - Monitoring Studio does not read the monitored file from the beginning anymore if this file was temporarily inaccessible. It will instead carry on from the position it was at the last polling once the file is accessible again. This has been modified to prevent false alerts when a network is temporally unaccessible |
File System Monitoring
| • | SWSY-115 - The file system monitoring feature did not work on UNIX if the file system name contained a special character. |
| • | SWSY-115 - On UNIX / Linux systems, an incorrect file system name was displayed in the interface if a mount device name was more than 20 characters long. Selecting this file system would lead to false alerts. |
HTTP Request
| • | SWSY-402 - An error was returned when the execution time was in a scientific format; a format which cannot be interpreted by PATROL. The response time is now reformatted to an actual number to allow the PATROL Agent to properly interpret them. |
| • | SWSY-300 - HTTP Request did not work on UNIX and Linux because of an issue in the sopen() PSL function executed by the PATROL Agent. A workaround has been implemented. |
Java MBean Polling (JMX)
| • | P1320 - JMX polling failed to reconnect to the WebLogic server when a regular expression was used in the key property and the server was restarted. |
| • | SWSY-159 - Attributes containing more than one line are now supported. |
Numeric Value Extraction
| • | SWSY-229 - The Numeric Value Extraction tool removed the [ and ] characters from the list of possible column separators. |
OS Commands
| • | SWSY-48 - The Command Line Analysis tool ignored the last line of a text file if it was empty or if no Exit Status was configured. |
Text Pre-Processing
| • | SWSY-154 - The end of a multi-line record could not be found if a regular expression was used to mark the start of this record and if the regular expression marking its end was empty line ("^$"). |
WBEM Queries
| • | SWSY-407 - WBEM queries were not supported on Windows Systems. |
| • | SWSY-514 - An alert is triggered on the QueryStatus parameter and an appropriate message is displayed if Java is unavailable on the server. |
Windows Events Monitoring
| • | SWSY-40 - Some instances stayed offline when monitoring Windows events from multiple event logs. Only the first event log was taken into account by Monitoring Studio. The other event logs were ignored which lead the KM to fail collecting events notified by the other event logs. |
| • | SWSY-391 - Windows events were not correctly collected when a monitored event source name contained special characters in a regular expression. |
| • | SWSY-487 - A detection delay could sometimes be observed for Windows Events. |
WMI Queries
| • | SWSY-100 - When using specific user-defined credentials to perform a WMI query, the username was not stored in PATROL configuration preventing the query to be executed |
| • | P1270 - It is now possible to query 64 bit VMI classes. |
Miscellaneous
| • | SWSY-17 - The Numeric Value Extraction KM Command triggered invalid alerts when a regular expression had no matching value. |
| • | SWSY-19 - The Debug feature fully supports OpenVMS. |
| • | SWSY-45 - "Invalid username/password" error messages were displayed in the System Output Windows of the PATROL Console when using PATROL Agent v9.0.00 and higher on Windows systems and when the default account was configured with a domain account. |
| • | SWSY-49 - The %{HTTP_RETURN_OUTPUT} macro is now returning the output of the HTTP request. |
| • | P1355 - No default PATROL ID was provided in the "File monitoring and analysis" and "File Security Check" dialog boxes. |
|
