# Enabling detailed errors logging

You may find it useful to enable detailed errors logging in the **AppServerX.xml** file in the following cases:

* providing more details for WebSpellChecker support requests;
* getting more details on issues and health diagnostics.

When enabling detailed logging, you need to ensure that the size of the log directory does not take too much disk space. Besides, we don’t recommend you to have logging enabled on a permanent basis. We also advise you to clear the logs directory content in a timely manner. For more details on disk space usage, refer to [Hardware requirements](broken://pages/cSwflyzl1OWUYIOSkNt0).

{% stepper %}
{% step %}

#### Open AppServerX.xml

Navigate to the AppServer folder.\
Open **AppServerX.xml** in a text editor.
{% endstep %}

{% step %}

#### Switch the log level to debug

Locate the **Log** tag.\
Inside it, find the [PrioritizationLevel](/v6.12.0/deployment/configuration/application-server/appserver-parameters.md#draft-appserverparameters-prioritizationlevel) tag.\
Change the value from **information** to **debug**.

```xml
<Log>
	<PrioritizationLevel>debug</PrioritizationLevel>
</Log>
```

Save the file.
{% endstep %}

{% step %}

#### Restart AppServer

Restart AppServer to apply changes in `AppServerX.xml`.

To restart: [stop](https://docs.wproofreader.com/v6.12.0/deployment/configuration/application-server/pages/IA2KNQLXDh85TwDivL4y#mainappservercommands-stopappserverwindowslinux2.stopappserver) the application, then [start](https://docs.wproofreader.com/v6.12.0/deployment/configuration/application-server/pages/IA2KNQLXDh85TwDivL4y#mainappservercommands-startappserverwindowslinux1.startappserver) it again.

Use [Main AppServer commands](/v6.12.0/deployment/configuration/application-server/main-appserver-commands.md).
{% endstep %}

{% step %}

#### Collect logs (if needed)

Review logs in the **AppServer/Log** files directory.\
Archive the whole directory as `.zip` and share it with support.
{% endstep %}
{% endstepper %}

#### Enabling advanced logging options <a href="#draft-enablingdetailederrorslogging-enablingadvancedloggingoptions" id="draft-enablingdetailederrorslogging-enablingadvancedloggingoptions"></a>

You can also enable additional logging options to get more information from your logs. Refer to a code sample description of the AppServerX.xml file below for details.

```xml
<Log>
	<!-- Size parameter defines the maximum size of the AppServerX.log file in kilobytes. If the maximum size is reached, a new log file will be created and the previous one will be saved with appropriate time stamp (log rotation). -->
 	<Size>10000</Size>
	<!-- Log prioritization level. Possible values (from the highest priority to the lowest): none, fatal, critical, error, warning, notice, information, debug, trace. The default is "information" -->
	<PrioritizationLevel>information</PrioritizationLevel>
	<!-- Possible values: all or general, threadpool, licensing, failsafe, selector, responder or values delimited by comma(,). 
The default is "all" -->
	<Subsystems>all</Subsystems>
</Log>
```

In the code sample above:

* [Size](/v6.12.0/deployment/configuration/application-server/appserver-parameters.md#draft-appserverparameters-size) tag is used to define the maximum file of AppServerX.log file in kilobytes.
* [Subsystems](/v6.12.0/deployment/configuration/application-server/appserver-parameters.md#draft-appserverparameters-subsystems) tag is used to specify the logs filter. Each log entry is generated by a particular system. You can use one of the available options to enable recording the logs for the selected subsystem only. By default, **all** value is selected meaning all subsystems record their messages into the log files directory.


---

# Agent Instructions: 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://docs.wproofreader.com/v6.12.0/deployment/configuration/application-server/enabling-detailed-errors-logging.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.