Upgrading from Monitoring Studio version 9.0, 9.1, 9.2 or 9.3.00
Monitoring Studio now requires Java v.1.8.00 or higher to operate properly. If the suitable version of Java is not detected, Monitoring Studio will stop and an error will be triggered by the Monitoring Studio Collection Error Count attribute.
|
What's New
| • | SWSY-2991: The new snmpRetryIntervals configuration variable has been added to Monitoring Studio to specify the interval (in milliseconds) at which the SNMP client must retry its requests until a response is received or the timeout is reached. |
Changes and Improvements
| • | SWSY-1883: The database queries overall performance (Oracle, MS SQL, MySQL or PostgreSQL servers) has been improved to reduce system resource consumption (memory and CPU) and runtime. The following changes have been applied to the Database Query Monitors: |
| ▪ | Microsoft SQL Database: The fields for providing either the Instance Name or the Port Number required to identify the SQL instance or the port number to use to monitor a specific SQL database have been merged. These two information being independent but not complementary the interface is now simplified. Any Microsoft SQL Database Monitor created with previous versions or Monitoring Studio will remain identified by the Instance Name or the Port Number according to the information provided upon their creation. |
| ▪ | The generic ODBC database connection is no longer supported. It is replaced with a generic Other (JDBC) database connection. Important: Any Monitor created for ODBC databases with previous versions of Monitoring Studio will be lost upon migration. |
| ▪ | Database Query Monitors now support the execution of SQL statements that return several record sets. |
| ▪ | Monitoring Studio now supports Oracle database v12. |
| ▪ | The output of PRINT statement and other SQL warnings is now reported in the result of the query. |
| ▪ | Also, user names in the form of domain\username are now fully supported on Microsoft SQL servers. |
| • | SWSY-2420: While Monitoring Studio v.9.x would automatically be set to CMA mode when a BMC TrueSight server was detected upon discovery; Monitoring Studio v.9.4.00 needs to detect a CMA policy with a Monitoring Studio configuration to switch to CMA mode. |
| • | SWSY-2422: Monitoring Studio has been improved to make it less I/Os intensive and to gain in performance and rapidity. |
| • | SWSY-2727: Web Request Monitor: It is now possible to better specify advanced properties for the HTTP request (HTTP headers, HTTP verb, credentials, etc.). |
| • | SWSY-2796/2715: Command Line Monitoring (Studio Command Line): The Exit Code and Exit Status attributes are deactivated for never-ending commands and commands for which no exit code is specified or when the exit code is ignored. Also, the Execution Time attribute is deactivated for never-ending command lines to avoid meaningless alerts. |
| • | SWSY-2808: The Numeric Value Extraction Monitor now supports numeric values expressed in size and time units through the Convert unit option that converts size and time units to bytes and seconds respectively. |
| • | SWSY-2826: Configuring Monitoring Studio to monitor multiple DB queries could cause performance issues on the PATROL Agent because of the high amount of memory consumed by multiple Java processes. |
| • | SWSY-2828: The Folder Monitor overall performance has been improved for folders containing a large number of files. Former folder limit is set to collect the contents of a folder within the configured timeout (Default: 30 seconds). |
| • | SWSY-2937: Monitoring Studio now requires Java v.1.8 or higher to operate properly. |
| • | SWSY-2975: The size of the header buffer used by SSH, SNMP, WBEM or HTTP request has been increased to ensure the proper execution of requests producing large result outputs. |
| • | SWSY-3063: Windows systems monitoring: Monitoring Studio has been improved to faster access executables and scripts on Windows systems and therefore improve the speed of collection cycles. |
| • | MATSYA-459: Monitoring Studio now better detects Java Runtime Environments (JREs) on Microsoft Windows, Linux, IBM AIX, HP-UX and Oracle Solaris. |
Fixed Issues
| • | SWSY-2422: In rare cases, the name of the temporary file used by Monitoring Studio could contain over 256 characters. This would lead to errors during the collect, especially when using Text Transforms in combination with Numeric Value Extractions or String Searches. |
| • | SWSY-2439: An event is now automatically generated when the Collection Error Count (Monitoring Studio) attribute triggers an alert. Its description is identical to the graph annotation. |
| ▪ | SWSY-2797: The Folder Monitor now properly reports all discovered files on Windows systems. |
| ▪ | SWSY-2468: Some of the Folder Monitor attributes were not considering time zone offsets and therefore reported incorrect values. The Last Modified File Elapsed Time, Longest Time File Remains In Folder and Oldest Modified File Elapsed Time attributes are now correctly calculated regardless of timezone differences. |
| • | SWSY-2561: SNMP Polling: Monitoring Studio failed to properly detect and interpret SNMP Counter and Timeticks-type OIDs. |
| • | SWSY-2783: Monitoring Studio has been fixed to properly process SHA authentication scheme with SNMP version 3. |
| • | SWSY-2789: When parsing the content of files on remote Linux or UNIX systems over SSH, extraneous data was retrieved, causing redundant and overlapping content to be parsed. |
| • | SWSY-2876: The Multi-Parameter Formula Monitor now properly collects results for String Search, Numeric Value Extraction and Text Transform Monitor instances attached to a Multi-Parameter Formula Monitor instance. Also, String Search, Numeric Value Extraction and Text Transform Monitor instances are now properly copied or deleted. |
| • | SWSY-2944: The Command Line Monitor: The method used to report the exit status from a return output has been changed to avoid any error in interpreting the command line exit code. |
| • | SWSY-2964: The default alert action macro %{SEN_ALERT_DEFAULTCONTENT} has been modified to only report on the attribute's name and the attribute's status (%{SEN_PARAMETER_STATUS}; %{SEN_PARAMETER_NAME) when used at the Group level. All other information have been removed as they were not relevant for Groups. |
| • | SWSY-3110/3116: Windows Event Logs Monitoring: |
| ▪ | The executable file used to query local and remote event logs on Windows system failed when the PATROL Agent installation path (%PATROL_HOME%) uses Windows long name format with spaces in the folder path (ex: C:\Program Files (x86)\BMC Software\Patrol3\ instead of equivalent short name like C:\PROGRA~2\BMCSOF~1\Patrol3\). |
| ▪ | When the string for a monitored Windows Event Log Provider contains special reserved regular expression characters, the event could not always be detected and the monitoring process could fail. |
| • | SWSY-3132: On Windows systems, Monitors using UNC paths containing share names were not properly monitored. |
| • | SWSY-3145: The Count attribute now properly reports on any process that match the user-defined criteria, regardless of their relationship. |
| • | MATSYA-535: The authentication process for Java modules failed when the specified password was shorter than 6 characters. |
|
