What objects and counters can be used in combination threshold policies
Only some performance counters can be used together in combination policies. When primary and secondary performance counters are specified, both performance counters must exceed their maximum limits before an event is generated.
| Primary storage object and counter | Secondary storage object and counter |
|---|---|
| Volume Latency | Volume IOPS |
| Volume MB/s | |
| Aggregate Utilization | |
| Aggregate Performance Capacity Used | |
| Node Utilization | |
| Node Performance Capacity Used | |
| Node Performance Capacity Used - Takeover | |
| LUN Latency | LUN IOPS |
| LUN MB/s | |
| Aggregate Utilization | |
| Aggregate Performance Capacity Used | |
| Node Utilization | |
| Node Performance Capacity Used | |
| Node Performance Capacity Used - Takeover |
Note
When a volume combination policy is applied to a FlexGroup volume, instead of to a FlexVol volume, only the
Volume IOPSand
Volume MB/sattributes can be selected as the secondary counter. If the threshold policy contains one of the node or aggregate attributes, then the policy will not be applied to the FlexGroup volume, and you will receive an error message describing this case. This is because FlexGroup volumes can exist on more than one node or aggregate.
Give documentation feedback