> 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/desktop-client/user-administration/statistics.md).
# Statistics
Monitor user login activity, failed attempts, and license usage in the Statistics view. Filter by timeframe and access detailed data on login issues and user status for effective administration.
The Statistics view in the User Administration gives you an overview of the last login attempts, failed login attempts and maximum license usage. The time period can be set to 7 days, 31 days or 365 days. The Login Problems section lists failed logins with timestamps and the reason (e.g. no license assigned), and the Last Logins section lists all user logins with additional information such as the time of the login, the license used, and whether the user is still logged in.
In addition, users whose logins were unsuccessful are highlighted in bold. More information about the reason for the failed login can be found in the table above.
---
# 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/desktop-client/user-administration/statistics.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.
