> For the complete documentation index, see [llms.txt](https://docs.aqua-cloud.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aqua-cloud.io/documentation/installation-for-on-premise/monitoring.md).

# Monitoring

Learn how to monitor your on-premise aqua server’s CPU, RAM, disk, and API login functionality for optimal performance and user access reliability.

We recommend monitoring CPU, RAM and hard disk of your aqua server. Furthermore, if you want to monitor whether users are able to login to aqua, you can consider simulating a login via API. The default address of the SOAP API is as follows:&#x20;

*`http://"yourhost"/aquaAPI/mainservice.asmx`*&#x20;

or

`http://"yourhost"/aquaAPI/mainservice.asmx?wsdl`\
\
The required service requests are *login* and *logout*. You can create an API User in aqua, which is allowed to login and logout. If the login is successful, a session code is returned, otherwise a stack trace error message might be returned. Do not forget to call logout after a successful login.\ <br>


---

# 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.aqua-cloud.io/documentation/installation-for-on-premise/monitoring.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.
