What's New
| • | Configuration Report Output Format: Two output formats were added to the configuration report: XLM and CSV |
| • | SW_SNMP_POLLING: New parameters were added: |
| ▪ | Delta to display the difference between values collected during two consecutive polling |
| ▪ | DeltaPerSecond to display the value corresponding to "Delta" divided by the elapsed time in seconds between the collection times |
| • | SW_JMX: New parameters were added: |
| ▪ | Delta to display the difference between values collected during two consecutive polling |
| ▪ | DeltaPerSecond to display the value corresponding to "Delta" divided by the elapsed time in seconds between the collection times |
| • | SW_NUMBERS: New parameters were added: |
| ▪ | Delta to display the difference between values collected during two consecutive polling |
| ▪ | DeltaPerSecond to display the value corresponding to "Delta" divided by the elapsed time in seconds between the collection times |
| • | %{NTEVENT_LAST_MATCHING_CONTENT}: This Application Class macro displays the content of the NT event. |
| • | Trigger a KM Discovery: This command forces a discovery of all objects for the monitored system. |
| • | Java MBean Polling (JMX): The feature now supports the polling of WebSphere v.7.x environment. |
Changes and Improvements
| • | Configuration report per container: This option is no longer available. The configuration report now takes the entire configuration into account. |
| • | Application Constants: Application Constants are now interpreted by the user interface. The interpretation upon collection is also processed as previously. |
| • | Discovery interval: It can now be customized from once every 5 minutes to once every 24 hours |
| • | Dynamic Objects: Dynamic thresholds can now be applied to dynamic objects. |
| • | Import/Export Configuration: These two KM Commands were moved to the Configuration menu command |
Fixed Issues
| • | DYNAMIC_RETURN_OUTPUT: It now properly returns the Dynamic extracted line value. |
| • | Polling Interval: Display object report did not show the correct polling interval when the interval was set to once a day or once a week. |
| • | File Monitoring and String Search: The monitoring and parsing of LOG files on OpenVMS servers have been improved. The ftell() PSL function does not always return the proper position in the file being monitored: a workaround as been implemented. The OpenVMS BACKUP command would also sometimes restore previously deleted temporary files. This would prevent Monitoring Studio from parsing the new file content. |
| • | SNMP Polling: When looking for a String or extracting a Numeric Value, the data was not properly parsed. |
| • | Dynamic Objects: In some cases the regular expression engine run by Monitoring Studio on the dynamic object class to perform a data extraction would let unwanted data to be used to build dynamic objects.
An issue occurred in some environments where the “view parameter output" button in the Monitoring Studio Dynamic Object wizard was empty.
An internal conflict could occur in the creation process of dynamical Patrol Object ID that led to the dynamical objects not being created. |
| • | JMX Polling: This feature has been greatly optimized and uses less resources than the previous version. |
| • | Numeric Extraction: This feature now supports numeric values with implicit 0. ( i.e.: value " .45" is seen as " 0.45" ). |
|
