···228229_Note: Your PDS will need to be restarted with those variables. This varies depending on your setup. If you followed this installation guide, run `systemctl restart pds`. You might need to restart the server or recreate the container, depending on what you are using._
2300000000000000000000000231### Updating your PDS
232233It is recommended that you keep your PDS up to date with new versions, otherwise things may break. You can use the `pdsadmin` tool to update your PDS.
···228229_Note: Your PDS will need to be restarted with those variables. This varies depending on your setup. If you followed this installation guide, run `systemctl restart pds`. You might need to restart the server or recreate the container, depending on what you are using._
230231+### Logging
232+233+By default, logs from the PDS are printed to `stdout` and end up in Docker's log. You can browse them by running:
234+235+```
236+[sudo] docker logs pds
237+```
238+239+Note: these logs are not persisted, so they will be lost after server reboot.
240+241+Alternatively, you can configure the logs to be printed to a file by setting `LOG_DESTINATION`:
242+243+```
244+LOG_DESTINATION=/pds/pds.log
245+```
246+247+You can also change the minimum level of logs to be printed (default: `info`):
248+249+```
250+LOG_LEVEL=debug
251+```
252+253### Updating your PDS
254255It is recommended that you keep your PDS up to date with new versions, otherwise things may break. You can use the `pdsadmin` tool to update your PDS.