# Serilog The third section allows us to set the Infoport logging. [](https://doc.eainfoport.cz/uploads/images/gallery/2024-04/snimek-obrazovky-2024-04-23-144643.png) The first item is a check box that says whether user activities should be logged. (List of visited URLs). [](https://doc.eainfoport.cz/uploads/images/gallery/2022-03/insighs.png) In the second item, we choose the relative path for saving logs. [](https://doc.eainfoport.cz/uploads/images/gallery/2022-03/log-path.png) In the third item, we select the type of logging. (Each type is described in the table. We recommend Information logging.) [](https://doc.eainfoport.cz/uploads/images/gallery/2022-03/logtype.png) Table for logging types.
**Level (from the most detailed to the least detailed)** | **Description** |
Verbose | For information that's typically valuable only for debugging. These messages may contain sensitive application data and so shouldn't be enabled in a production environment. Disabled by default. |
Debug | For information that may be useful in development and debugging. Example: Entering method Configure with flag set to true. Enable Debug level logs in production only when troubleshooting, due to the high volume of logs. |
Information | For tracking the general flow of the app. These logs typically have some long-term value. Example:Request received for path/api/todo |
Warning | For abnormal or unexpected events in the app flow. These may include errors or other conditions that don´t cause the app to stop but might need to be investigadet. Handled exceptions are a common place to use the Warning log level. Example: FileNotFoundException for file quotes.txt. |
Error | For errors and exceptions that cannot be handled. These messages indicate a failure in the current aktivity or operation (such as the current http request), not an app-wide failure. Example log message: Cannot insert record due to duplicate key violation. |
Fatal | For failures that require immediate attention. Examples: data loss scenarios, out of disk space. |