Changes and Improvements
| • | It is now possible to configure specific alert actions to be executed when a problem occurs. |
| • | Definitions for the Available Capacity and Subscribed Capacity attributes of the Hitachi Disk Array monitor type have been updated to better reflect the actual calculation method used to report on these attributes. |
| • | The debug file now stores additional critical information, warning and error messages when the debug mode is activated. |
| • | In order to optimize the monitoring on large environment, users can now customize the discovery and the collect timeouts directly from the user interface. See the Setting Discovery and Collect Timeouts section for detailed information. |
Fixed Issues
| • | An erroneous calculation method lead Hitachi Storage Monitoring to report wrong values for the Operation Rate attributes for Disk Arrays and Volumes. |
| • | An error could sometimes occur when the Status of a Disk Array is unavailable. |
| • | The value reported for the Operation Rate attribute of Fiber Ports was inaccurate due to a time's conversion error. |
| • | Before each re-initialization, Hitachi Storage Monitoring backs-up the latest PATROL Agent configuration and save the data in a timestamped configuration file. The number of configuration backup files can rapidly use a large amount of space on a server. To avoid this situation, Hitachi Storage Monitoring will now only save the latest configuration backup under the %PATROL_HOME%\config directory. |
| • | No instances were created in the console when using a version of the PATROL Agent lower than v.9.5. This issue is now fixed. |
| • | When the monitoring of volumes is disabled, the Consumed Capacity and Consumed Capacity Percentage attributes are now still collected at the Storage Pools level. |
| • | Hitachi Storage Monitoring failed to collect data when the Hitachi Device Manager refresh frequency was set to Every Hour or Once a Day. |
|
