> For the complete documentation index, see [llms.txt](https://docs.weka.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.weka.io/3.14/overview.md).

# Weka System Overview

- [About the WEKA System](https://docs.weka.io/3.14/overview/about.md): Weka is a software solution that enables the implementation of a shareable, scalable, distributed file storage system.
- [SSD Capacity Management](https://docs.weka.io/3.14/overview/ssd-capacity-management.md): Understand the key terminologies relating to Weka system capacity management and the formula for calculating the Weka system net data storage capacity.
- [Filesystems, Object Stores & Filesystem Groups](https://docs.weka.io/3.14/overview/filesystems.md): This page describes the three types of entities relevant to data storage in the Weka system: filesystems, object stores and filesystem groups.
- [Weka Networking](https://docs.weka.io/3.14/overview/networking-in-wekaio.md): This page reviews the theory of operation for Weka networking.
- [Data Lifecycle Management](https://docs.weka.io/3.14/overview/data-storage.md): This page covers the principles for data lifecycle management and how data storage is managed in SSD-only and tiered Weka system configurations.
- [Weka Client & Mount Modes](https://docs.weka.io/3.14/overview/weka-client-and-mount-modes.md): Understanding the Weka system client and possible mount modes of operation in relation to the page cache.
- [Glossary](https://docs.weka.io/3.14/overview/glossary.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.weka.io/3.14/overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.