Upgrading from Monitoring Studio KM for PATROL 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 CollectionErrorCount parameter.
|
What's New
| • | SWSY-2646: A new KM command, Value Map (SEN_MS_VALUEMAP), is now available to extract values from result outputs of other Monitors and map these values to user-defined status that match your specific needs. |
| • | SWSY:2721: Command Line Monitor: The monitor now offers two separated procedure to execute command line locally and remotely. |
| • | SWSY-3006: A new KM command, Value Map Template (SEN_MS_DYNAMICVALUEMAP), is now available to extract values from result outputs of other Monitors and map these values to user-defined status that match your specific needs. While mostly similar to the Value Map KM command, the Value Map Template is designed to create instance dynamically. |
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 are 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-2400: The Dynamic prefix is no longer added to labels (display names) for Dynamic String Search and Dynamic Numeric Value Extraction instances to make labels shorter and easier to read. |
| • | SWSY-2410: Dynamic Objects: Monitoring Studio now allows users to display a detailed or simplified view of the dynamic objects hierarchy in the PATROL Console by using the Hide/Show Template KM Command added to the Dynamic Object Builder instances (SEN_MS_DYNAMICDISCOVERY). |
| • | 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 aMonitoring 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-2439: An event is now automatically generated when the CollectionErrorCount (SEN_MS_MAIN) parameter triggers an alert. Its description is identical to the graph annotation. |
| • | SWSY-2476: Text Pre-processing: JSON to CSV conversion now supports user-defined separators. |
| • | SWSY-2496: String Searches: Monitoring Studio allows you to skip blank lines while performing a string search. This option is particularly useful when searching for lines that do not contain a specific string, as blank lines would match this criteria. |
| • | SWSY-2557: Dynamic Instances can now handle output files containing multiple lines with the same IDs. Users can specify the way the product manages these lines (keep the first or last line found or group all lines together). |
| • | SWSY-2582:Monitoring Studio can now import Icinga 1 (icinga.cfg) configuration files through the Import Nagios Configuration process. |
| ▪ | SWSY-2721: Monitoring Studio now fully supports local command execution with option to run continuously while monitoring remote hosts. |
| ▪ | SWSY-2796/2715: The ExitCode and ExitStatus parameters are deactivated for never-ending commands and commands for which no exit code is specified or when the exit code is ignored. Also, the ExecutionTime parameter is deactivated for never-ending command lines to avoid meaningless alerts. (SEN_MS_COMMANDLINE). |
| • | 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-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-2828: The Folder Monitor overall performance has been improved for folders containing a large number of files. Former folder limit (folderLimit) is removed and changed to collect the contents of a folder within the configured timeout (Default: 30 seconds). |
| • | SWSY-2829: The Agent's Default Account can now be selected for executing Nagios plugin commands on the local Nagios server. |
| • | SWSY-2924: The process of importing a Nagios configuration has been simplified to only require the Nagios credentials that Monitoring Studio will use to run all Nagios Plugin commands on the Nagios server (if no credentials are provided, the PATROL Agent default account is used). |
| • | SWSY-2937: Java settings: |
| ▪ | Java settings are now taken into account dynamically and no longer require a restart of the PATROL Agent. |
| ▪ | It is now possible to specify the Java heap memory settings (minimum and maximum) from the Advanced Settings of the Java Settings. |
| ▪ | Monitoring Studio now requires Java v.1.8 or higher to operate properly. |
| • | 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. |
| • | 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-2468: Some of the Folder Monitor parameters were not considering time zone offsets and therefore reported incorrect values. The LastModifedFileElapsedTime, LongestTimeFileRemainsInFolder and OldestModifiedFileElapsedTime parameters are now correctly calculated regardless of time zone differences. |
| • | SWSY-2561: SNMP Polling: Monitoring Studio now properly detects and interpret SNMP Counter and Timeticks-type OIDs. Note that this fix does not apply to imported configurations or Monitors created before the upgrade to version 9.4.00. |
| • | SWSY-2648: Thresholds set on Numeric Value Extraction instances for Dynamic Instances, saved in the configuration could not be properly exported and imported. |
| • | SWSY-2901: Thresholds set on Numeric Value Extraction templates (Dynamic Instances) were not immediately taken into account. Monitoring Studio now triggers a new discovery at the end of the Threshold setting process (Wizard) to apply the user-defined thresholds. |
| • | SWSY-2846: Dynamic Numeric Value Extraction: Monitoring Studio now properly extracts numeric values from DOS format files. |
| • | 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-2797: Folder Monitoring: The Folder Monitor now properly reports all discovered files on Windows systems. |
| • | SWSY-2876: The Multi-Parameter Formula 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 instances are now properly copied or deleted. |
| • | SWSY-2902: The following macros were not properly set on alert actions defined for Dynamic Numeric Value Extractions and Dynamic String Search instances: |
| ▪ | Host-type Macros: %{SEN_HOST_DOMAIN}, %{SEN_HOST_FQDN}, %{SEN_HOST_IPADDRESS}, %{SEN_HOST_NAME}, %{SEN_HOST_SNMPCOMMUNITY}, %{SEN_HOST_SYSTEMTYPE} |
| ▪ | Group-type Macros: %{SEN_GROUP_CLASS}, %{SEN_GROUP_COLLECTIONERRORS}, %{SEN_GROUP_CONTACT}, %{SEN_GROUP_DESCRIPTION}, %{SEN_GROUP_ID}, %{SEN_GROUP_LABEL}, %{SEN_GROUP_TYPE} |
| • | SWSY-2937: Monitoring Studio no longer displays a message in the System Output Window when the Java Collection Hub is started as a specific user. |
| • | 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 parameter's name and the parameter'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 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 (such as $), 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 and MatchingProcesses parameters now properly report on the matching processes according to 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. |
|
