# Diagnostics Settings

The diagnostics settings panel can be used to control the logging infrastructure in the SanteDB iCDR host server. The configuration panel provides an enumeration of the registered log sources and allows administrators to set each log level for independent services.

![](/files/U0AkntxaxCfezqoFiJEW)

The writers section allows for the setting of an output method for the diagnostic sources.

| Writer                        | Description                                                                                                       | Initialization Data          |
| ----------------------------- | ----------------------------------------------------------------------------------------------------------------- | ---------------------------- |
| ConsoleTraceWriter            | Outputs diagnostic logs to the console. Only useful for running SanteDB in console mode.                          |                              |
| RolloverTextWriterTraceWriter | Outputs diagnostics logs to a file on the disk.                                                                   | The filename of the log file |
| SystemDiagnosticsTraceWriter  | Emits diagnostics logs to the System Debugging output. In Windows you can use dbgview\.exe to see these messages. |                              |
| EventLogTraceWriter           | Emits diagnostics logs to the SanteDB diagnostics event source in the Windows Event Log                           |                              |

Additionally, the global filter can be set for the writer, or each trace source.

<table><thead><tr><th width="204.8537906426409">Log Level</th><th width="397.69210383167945">Contents</th></tr></thead><tbody><tr><td>LogAlways</td><td>Any log which is generated by the component is emitted to the diagnostic writer.</td></tr><tr><td>Verbose</td><td>Detailed logging is enabled. This include errors, warnings, critical service faults, debugging information, enter/exit events.</td></tr><tr><td>Informational</td><td>Logs should contain errors, warnings, critical faults, and high level diagnostic information such as status of jobs, message issues, etc.</td></tr><tr><td>Warning</td><td>Logs should only contain warnings, errors and critical service faults. Warnings are typically errors which can be safely ignored or don't result in failed transactions.</td></tr><tr><td>Error</td><td>Logs should only contain errors and critical service faults. Errors are exceptional cases which cause transactions to not be processed.</td></tr><tr><td>Critical</td><td>Logs should only contain data related to critical system failures where the SanteDB host process stops or becomes unresponsive.</td></tr></tbody></table>


---

# 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://help.santesuite.org/operations/server-administration/configuration-tool/diagnostics-settings.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.