# Serilog

The third section allows us to set the Infoport logging.

[![Snímek obrazovky 2024-04-23 144643.png](https://doc.eainfoport.cz/uploads/images/gallery/2024-04/scaled-1680-/snimek-obrazovky-2024-04-23-144643.png)](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).

[![insighs.png](https://doc.eainfoport.cz/uploads/images/gallery/2022-03/scaled-1680-/insighs.png)](https://doc.eainfoport.cz/uploads/images/gallery/2022-03/insighs.png)

In the second item, we choose the relative path for saving logs.

[![Log path.png](https://doc.eainfoport.cz/uploads/images/gallery/2022-03/scaled-1680-/log-path.png)](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.)

[![logtype.png](https://doc.eainfoport.cz/uploads/images/gallery/2022-03/scaled-1680-/logtype.png)](https://doc.eainfoport.cz/uploads/images/gallery/2022-03/logtype.png)

Table for logging types.

<table id="bkmrk-%C3%9Arove%C5%88-%28od-nejpodrob" style="height: 471.641px; width: 822px;" width="0"><tbody><tr style="height: 80.1719px;"><td class="align-center" style="height: 80.1719px; width: 151.75px;">**Level (from the most detailed to the least detailed)**

</td><td class="align-center" style="height: 80.1719px; width: 669.25px;">**Description**

</td></tr><tr style="height: 57.7812px;"><td style="height: 57.7812px; width: 151.75px;">Verbose

</td><td style="height: 57.7812px; width: 669.25px;">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.

</td></tr><tr style="height: 80.1719px;"><td style="height: 80.1719px; width: 151.75px;">Debug

</td><td style="height: 80.1719px; width: 669.25px;">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.

</td></tr><tr style="height: 57.7812px;"><td style="height: 57.7812px; width: 151.75px;">Information

</td><td style="height: 57.7812px; width: 669.25px;">For tracking the general flow of the app. These logs typically have some long-term value. Example:Request received for path/api/todo

</td></tr><tr style="height: 80.1719px;"><td style="height: 80.1719px; width: 151.75px;">Warning

</td><td style="height: 80.1719px; width: 669.25px;">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.

</td></tr><tr style="height: 80.1719px;"><td style="height: 80.1719px; width: 151.75px;">Error

</td><td style="height: 80.1719px; width: 669.25px;">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.

</td></tr><tr style="height: 35.3906px;"><td style="height: 35.3906px; width: 151.75px;">Fatal

</td><td style="height: 35.3906px; width: 669.25px;">For failures that require immediate attention. Examples: data loss scenarios, out of disk space.

</td></tr></tbody></table>

In the fourth item, we select where we want the logs to be written. We have three options: Console, File or Both.

[![service log write to.png](https://doc.eainfoport.cz/uploads/images/gallery/2022-03/scaled-1680-/service-log-write-to.png)](https://doc.eainfoport.cz/uploads/images/gallery/2022-03/service-log-write-to.png)

In the fifth item, we choose how often the log file should be closed.

[![rollinginterval.png](https://doc.eainfoport.cz/uploads/images/gallery/2022-03/scaled-1680-/rollinginterval.png)](https://doc.eainfoport.cz/uploads/images/gallery/2022-03/rollinginterval.png)

Here we can see the chosen day. This means that a new log file is created for the portal every day. Logs from previous days remain on disk.

After filling in, just press the [![check.png](https://doc.eainfoport.cz/uploads/images/gallery/2022-03/scaled-1680-/check.png)](https://doc.eainfoport.cz/uploads/images/gallery/2022-03/check.png) button and the manager will tell you if everything is OK.