Introduction
WekaFS is a software-defined, scalable distributed file system designed for high-performance storage using standard x86 servers and NVMe SSDs, removing the need for specialized hardware. It delivers low latency, cloud scalability, and seamless integration with technologies like POSIX, NFS, SMB, S3, and GPUDirect Storage.
Key Features
- Performance: Optimized for AI/ML, Life Sciences, Financial Trading, and HPC workloads.
- Distributed Architecture: Fully distributed design enables robust performance and scalability.
- Data Services: Offers tiering, snapshots, clones, and cloud-bursting.
- Hybrid Cloud: Facilitates smooth transitions between on-premises and cloud environments.
- Ease of Use: Intuitive GUI for managing massive datasets effortlessly.
WekaFS ensures cost-effective, high-performance storage for demanding data environments.
To help you get started, here’s what you can do next:
- To explore what metrics this integration monitors, see Supported Metrics and Default Monitoring Configuration.
- To configure and check prerequisites, see Working with Weka.
Use Cases
Discovery
- Discovers all the high-level components such as Weka Cluster, Weka Cluster Server, Weka Drive, and Weka FileSystem
- Publishes relationships between resources to enable a topological view and simplify maintenance
- Refer to the Hierarchy of Weka resources 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 Version
| Supported Target Versions |
|---|
| Weka FS 4.4.0 |
Hierarchy of WEKA resources
- Weka Cluster
- Weka Cluster Server
- Weka Drive
- Weka FileSystem
- Weka Cluster Server
Version History
| Application Version | Bug fixes / Enhancements |
|---|---|
| 2.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. |
| 2.0.0 | Support added to the following metrics:
|
| 1.0.2 | Refined metric calculation logic for the following metrics:
|
| 1.0.1 |
|
| 1.0.0 | Initial application Discovery and Monitoring Implementations. |
×