> For the complete documentation index, see [llms.txt](https://4wsplatform.gitbook.io/user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://4wsplatform.gitbook.io/user-guide/modules/ee10-1-log-and-analysis.md).

# Log & Analysis

This module is used to monitor an application executed through Platform, from several points of view:

* monitor the **application log** generated on the server-side, like SQL queries, messages generated by server-side javascript actions, etc.
* analyze aggregated data from the application log, in order to  **log**  **statistics**  about server-side operations, such as CPU/memory consumption, HTTP requests
* **analyze the app**  behavior, from different perspectives, including queues and scheduled processes performance, resources consumption, grave misconfigurations, user sessions and threads, etc.
* monitor the **table log** , i.e. server-side log stored in a table and automatically generated for specific events, like javascript or mobile errors, SMS/email sendings, etc.
* **application threads**, including http requests pool, database connections pool, enqueued elements, scheduled processes, etc.
* **user sessions**, i.e. authenticated on-line users and creation date/time and session memory consumption
* **memory heap analysys**, in terms of total memory, consumed memory, free memory
* **heap memory consumption** , i.e. the amount of memory consumed by the app, in terms of data and metadata; this feature should be used carefully, since it consumes a lot of CPU and disk space and it can be helpful only in case of grave issues related to out of memory errors
* **data audit** , i.e. listening to data writing (insert, update and delete operations) defined per table. Once activated that listening for a specified set of tables, Platform automatically records any change internally. After that, you can access to these records through an ad hoc monitor panel, accessible through  **Administration -> Audit** .

This data can be used to identify bottlenecks in the application, misconfigurations or simply to tune the whole system.\
The first 4 functionalities can be accessed from within the Web Designer, through **Monitoring ->Log and Analysis**\
See the sub-sections for more information about each of these functionalities.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://4wsplatform.gitbook.io/user-guide/modules/ee10-1-log-and-analysis.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.