Introduction
Dell EMC Power Store is designed to deliver the performance, availability, automation and agility that modern applications require, while reducing complexity across hybrid cloud deployments.With VMware users in mind, PowerStore integrates seamlessly into VMware management frameworks to simplify storage management for administrators and increase overall efficiency.
To help you get started, here’s what you can do next:
- To explore monitored metrics, see Supported Metrics and Default Monitoring Configuration.
- To verify prerequisites and configure, see Working with Dell PowerStore.
Use Cases
Discovery
- Discovers all the high-level components such as Powerstore Storage Cluster, Powerstore Storage Appliance, Powerstore Storage Node, Powerstore Storage File System etc.
- Publishes relationships between resources to enable a topological view and simplify maintenance
- Refer to the Resource Hierarchy for detailed structure
Monitoring
- Provides monitoring related to availability, capacity, performance and usage.
- Alerts are generated when defined metric thresholds are breached, notifying users of potential issues.
- Refer to the Supported Metrics and Default Monitoring Configuration for complete details.
Supported Target Versions
| Version 3.6.1.3 | Version 3.6.1.2 | Version 3.5.0.1 |
| Version 3.6.1.0 | Version 3.6.0.0 | Version 2.0.0.0 |
| Version 3.2.0.1 | Version 2.1.0.0 | Version 4.0.1.0-2408234 |
Hierarchy of Dell Power Store resources
- Powerstore Storage Cluster
- Powerstore Storage Appliance
- Powerstore Storage Node
- Powerstore Storage Volume
- Powerstore Volume Group
- Powerstore Storage FC port
- Powerstore Storage ETH Port
- PowerStore Host
- Powerstore Host Group
- Powerstore NAS server
- Powerstore Storage File System
- Powerstore Storage Appliance
Version History
| Application Version | Bug fixes / Enhancements |
|---|---|
| 3.1.0 | This implementation introduces third-party CI alert mapping and OpsQL-based enhancements. Configure alert mappings to target CI systems through the application configuration. After configuration, the system automatically forwards alerts to the corresponding third-party platforms and maps them to the specified CIs, ensuring consistent integration and efficient alert management. Previously, resource filters in the app configuration required manual entry of resource core and custom attributes. With this enhancement, the configuration is moved to OpsQL-based filtering, where users can see the keys auto-populated as needed. |
| 3.0.0 |
|
| 3.1.0 | This implementation introduces third-party CI alert mapping and OpsQL-based enhancements. Configure alert mappings to target CI systems through the application configuration. After configuration, the system automatically forwards alerts to the corresponding third-party platforms and maps them to the specified CIs, ensuring consistent integration and efficient alert management. Previously, resource filters in the app configuration required manual entry of resource core and custom attributes. With this enhancement, the configuration is moved to OpsQL-based filtering, where users can see the keys auto-populated as needed. |
| 3.0.0 |
|
| 2.0.1 | Added code support for Get Target Response command for each native type. On demand latest snapshot support and Activity logger changes. |
| 2.0.0 | Initial deployment |