> For the complete documentation index, see [llms.txt](https://docs.akamas.io/quick-guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akamas.io/quick-guides/quick-guides-akamas-in-a-sandbox/aias-01-guide-explore-an-optimization-study-for-a-kubernetes-microservices-application/aias-01-explore-the-system.md).
# \[AIAS-01] Explore the System
From the "Systems" page, you can explore all the Systems within the sandbox. A System is the application being optimized; in our example, it is called "Auth service". You can get to this page either by selecting it on the sidebar or by following the link in the header of the opened Offline Study.
As you can see, the System is represented by several components, whose parameters and metrics you can explore:
* The JVM powering the application. In this example, we selected to optimize 5 common JVM parameters like heap size and garbage collector (click on the card for the full set of 61 parameters for the OpenJDK 11 runtime)
* The Kubernetes Container, whose parameters CPU and Memory limits and requests have all been selected in the optimization scope
* The Kubernetes Workload, which tracks deployment-level metrics like the number of pod replicas
* The Web Application, whose metrics are used to measure the impact of the configurations experimented during the study, including the cost and the application performance metrics
---
# 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.akamas.io/quick-guides/quick-guides-akamas-in-a-sandbox/aias-01-guide-explore-an-optimization-study-for-a-kubernetes-microservices-application/aias-01-explore-the-system.md?ask=&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.
