Dell PowerStore
Support
This ZenPack is developed and supported by Virtana. Enterprise support is available to Virtana customers with an active subscription or support agreement. ZenPacks are available at delivery.zenoss.com. To request more information about this or any other ZenPack, contact Virtana.
This ZenPack is developed and supported by Virtana Professional Services, and is a supplemental monitoring offering to the standard Virtana product subscription or support agreement. These are offered as separate subscriptions in order to provide initial setup, training, and ongoing compatibility and maintenance. All standard packages are renewable every 12 months from the date of purchase. Contact Virtana to request more information regarding this or any other ZenPacks.
Version
Version 1.0.2
Released June 23, 2026
Prerequisites
The following prerequisites are required before installing this ZenPack:
Prerequisite | Restriction |
|---|---|
Product | Zenoss 6.0.0 or higher |
Required ZenPacks | ZenPacks.zenoss.ZenPackLib >=2.1.1, ZenPacks.zenoss.PS.Util >=1.14.11, ZenPacks.zenoss.Pythoncollector |
Other dependencies | None |
Overview
This ZenPack adds monitoring for Dell PowerStore storage appliances and introduces a new device class: /Storage/Dell/PowerStore.
The ZenPack does the following:
Gathers active alerts from the cluster and converts them into events. These events don't clear automatically, so make sure they're included in the events to age, or that someone closes them manually.
Gathers status from most system components. Status values are converted into events, which clear when the status returns to healthy.
Gathers metrics from the cluster and components using two methods. A limited set of metrics is queried directly against each component; by default, these are queried every five minutes. A larger set of metrics is gathered by requesting the device to create a metrics archive containing all data since the last archive. The system then parses the datapoints from the archive. This process is resource-intensive for both the monitored device and the monitoring system, so by default it runs hourly.
Add devices
When you add a new PowerStore cluster, you don't need to set the manageIP on the device. You must configure the following zProperties:
Property | Description |
|---|---|
| The URL of the cluster, using either the API or hostname. You can include a port number if the cluster doesn't use the default port (80 or 443). Example: |
| Set to |
| Set to |
| Leave at the default ( |
| A user account with at least read-only access and the ability to request metrics archives. |
| Password for the user account specified in |
Configuration
This ZenPack uses the following zProperties to control its operation. Defaults are set on the device class and can be customized or overridden at the device class or device level.
Property | Description |
|---|---|
| Interval between alert queries to devices. Default: |
| Interval between individual metric and status queries to devices. Default: |
| Interval between metrics archive generation cycles. This process is resource-intensive for both the device and the collection process. Don't set this value too low. Default: |
Modeler plugins
This ZenPack includes the following modeler plugins:
zenoss.http.powerstore.Applianceszenoss.http.powerstore.HostsInitiatorszenoss.http.powerstore.VolumeGroups
Device class templates
Devices/Storage/Dell/PowerStore
This section describes the monitoring templates available under the Devices/Storage/Dell/PowerStore device class.
Node
Graphs
Node IOPS
Node Latency
Datapoints
avgLatencyavgReadLatencyavgWriteLatencyreadIopstotalIopswriteIops
VolumeStats
Graphs
DEFAULTS
IOPS
Mirror Latency
Read Write Latency
Throughput
Total IOPS
Total Throughput
Volume Used Percent
Datapoints
avgMirrorOverheadLatencyavgMirrorWriteLatencyavgReadLatencyavgWriteLatencyDEFAULTSmirrorOverheadLatencymirrorWriteBytesmirrorWriteIopsmirrorWriteLatencypercentUsedreadBytesreadIopsreadLatencysizetotalBandwidthtotalIopsusedwriteByteswriteIopswriteLatency
Initiator
Graphs
DEFAULTS
IOPS
Read Write Latency
Throughput
Total IOPS
Total Throughput
Datapoints
avgReadLatencyavgWriteLatencyDEFAULTSreadBytesreadIopsreadLatencytotalBandwidthtotalIopswriteByteswriteIopswriteLatency
Appliance
Graphs
Appliance IOPS
Appliance Node Count
Avg IO Size
Avg IO Size - Overall
Data Reduction Detail
Efficiency Savings
IO Workload CPU
Logical Provisioned vs Used
Logical Used by Type
Mirror Latency
Physical Capacity
Physical Capacity - Total
Physical Utilization
Read Write Latency
Savings
Shared Space by Type
Throughput
Thresholds
Nodes
Datapoints
avgIoSizeavgLatencyavgMirrorOverheadLatencyavgMirrorWriteLatencyavgReadLatencyavgReadSizeavgWriteLatencyavgWriteSizedataPhysicalUseddataReductiondataReductionPctDEFAULTSefficiencyPctefficiencyRatioioWorkloadCpuUtilizationlogicalProvisionedlogicalUsedlogicalUsedFileSystemlogicalUsedVolumelogicalUsedVvolmirrorWriteBandwidthmirrorWriteIopsnodesphysicalTotalphysicalUsedphysicalUsedPctreadBandwidthreadIopsreducibleDatareducibleDataReductionreducibleDataReductionPctsharedLogicalUsedsharedLogicalUsedFilesystemsharedLogicalUsedVolumesharedLogicalUsedVvolsnapshotSavingssnapshotSavingsPctsystemFreeSpacethinSavingsthinSavingsPcttotalBandwidthtotalIopsunreducibleDatawriteBandwidthwriteIops
Drive
Graphs
Endurance Remaining
Thresholds
Minimum Endurance Critical
Minimum Endurance Error
Datapoints
enduranceRemaining
FCPort
Graphs
Avg IO Size
Avg IO Size - Overall
Current Logins
DEFAULTS
FC Link Errors
IOPS
Read Write Latency
Throughput
Total IOPS
Total Throughput
Unaligned IOPS
Unaligned Throughput
Thresholds
FC Dumped Frames
FC Invalid CRC
FC Invalid TX Word
FC Link Failure
FC Loss of Signal
FC Loss of Sync
FC Protocol Error
Datapoints
avgIoSizeavgLatencyavgReadLatencyavgReadSizeavgWriteLatencyavgWriteSizecurrentLoginsDEFAULTSdumpedFramesPsinvalidCrcCountPslinkFailureCountPslossOfSignalCountPslossOfSyncCountPsprimSeqProtErrCountPsreadBandwidthreadIopstotalBandwidthtotalIopsunalignedBandwidthunalignedIopsunalignedReadBandwidthunalignedReadIopsunalignedWriteBandwidthunalignedWriteIopswriteBandwidthwriteIops
Host
Graphs
DEFAULTS
IOPS
Read Write Latency
Throughput
Total IOPS
Total Throughput
Datapoints
avgReadLatencyavgWriteLatencyDEFAULTSreadBytesreadIopsreadLatencytotalBandwidthtotalIopswriteByteswriteIopswriteLatency
Device
Graphs
Avg IO Size
Avg IO Size - Overall
Data Reduction Detail
DEFAULTS
Efficiency Savings
IOPS
Logical Provisioned vs Used
Logical Used by Type
Mirror Latency
Physical Capacity
Physical Capacity - Total
Physical Utilization
Read Write Latency
Savings
Shared Space - Total
Shared Space by Type
Throughput
Total IOPS
Total Throughput
Datapoints
avgIoSizeavgLatencyavgMirrorOverheadLatencyavgMirrorWriteLatencyavgReadLatencyavgReadSizeAvgavgWriteLatencyavgWriteSizedataPhysicalUseddataReductiondataReductionPctDEFAULTSefficiencyPctefficiencyRatiologicalProvisionedlogicalUsedlogicalUsedFilesystemlogicalUsedVolumelogicalUsedVvolmirrorWriteBandwidthmirrorWriteIopsphysicalTotalphysicalUsedphysicalUsedPctreadBandwidthreadIopsreducibledataReductionPctreducibleDataReductionsharedLogicalUsedsharedLogicalUsedFilesystemsharedLogicalUsedVolumesharedLogicalUsedVvolsnapshotSavingssnapshotSavingsPctsystemFreeSpacethinSavingsthinSavingsPcttotalBandwidthtotalIopsunreducibleDatawriteBandwidthwriteIops
Changelog
1.0.2
Bug fixes
SVC-4102: Updated trap parsing transform.
1.0.1
Bug fixes
SVC-4101: Updated event class mappings, transforms, and event classes for templates. Updated the event class and
eventkeyfor alerts downloaded from device.
1.0.0
Initial release.