HPE Storage Plug-in for VMware vRealize Operations – StoreServ Disk Drive Tier and Symptom Definitio

[m_rieder]

We are using the latest version of VMware vRealize Operations (7.0) with the HPE Storage Plug-in (3.4.0).
Unfortunately we are experiencing some alert notifications by that plugin, which in our opinion need some improvements:

Port Latency Alert:

According to its Symptom Definition, the alert "HPE 3PAR FC Port Latency – Critical Alert" is triggered when the latency of an “HPE 3PAR StoreServ FC Port” Object Type is greater than 50ms (25ms for a Warning Alert). vROPS constantly shows up the alerts for two ports on two of our 3PARs. We found out, that these ports are the one, used for Remote Copy between those 3PARs. On the RC ports such a high latency it shouldn’t be a problem. The problem though is that all Ports are in the same vROPS Object Group and that no differentiation is made between the port types (Disk, Host, RC).

Disk Latency Alert:

A similar problem is the HPE 3PAR Disk Drive Latency Alert. The definitions trigger an alert when the disk drive latency is higher than 25ms (Warning) respectively 50 ms (Critical). But no differentiation between the disk types is made here either. For an SSD hard disk, a latency of 25ms is quite problematic, while this may happen with an NL hard disk. 
Also in this case all hard disks are combined in a group and a distinction for a more granular alarm setting is missing. Even the Treshold Alerts which can be defined in the StoreServ Management Console provide templates with a differentiation based on the disk type.

As workaround, we had the idea to create custom groups and defined customized alerts to these, but the disk object do not provide any properties to use for filter criteria.

Does someone has made similar experiences?

[Crakeen]

Same problem  here, how did you workaround this?