What's New
• | The new KM command "Acknowledge Alerts" allows the user to acknowledge all alerts for a specific instance |
• | Configuration Variables: Two new configuration variables were added respectively to the Web Request and the WBEM Queries application classes: |
▪ | /MASAI/SENTRY8/windowsWebRequestScriptPath: to specify the path to the VB script used to perform web requests on Windows servers |
▪ | /MASAI/SENTRY8/wbemJarPath: to specify the path to the jar file used to perform WBEM queries |
• | The macro %{FOLDER_OLDEST_REMAINING_FILE] has been added to the list of Alert Action Macros to provide the name of the oldest remaining file in the folder. |
Changes and Improvements
• | The Dynamic Object Builder option allows the user to define if and how Monitoring Studio must trigger an alert when the Dynamic Item, containing the extracted line, is missing from one collect to another has been improved to offer additional alert types: Trigger an INFORMATION, Trigger a WARNING, Trigger an ALARM. |
• | The way Monitoring Studio removes missing objects in the console can now be configured to : Never, As soon as they are missing or When they are missing "n" times in a row |
• | It is now possible to send an email alert action to multiple recipients |
• | The new parameter "LongestTimeFileRemainsInFolder" has been added to the SW_FOLDERS application class to displays the longest time an existing file has been placed in a folder |
Fixed Issues
• | HTTP Request did not trigger an alert when a username/password was configured and the web site was stopped |
• | Polling intervals and Alert Actions could not be set on older versions of the PATROL Agent because the "parameterType" instance variable was missing |
• | Exit Status Codes were not properly interpreted by the Monitoring Studio interface on older versions of the PATROL Agent |
• | SNMP OIDs: COUNTER-type values were not properly interpreted |
• | The JMX monitoring would stop working when the application server was restarted, resulting in high CPU usage |
|