# Where is the Designer log viewer diagnostics info stored? **URL:** \ **Category:** Ignition\ **Created:** [June 10, 2021, 2:07am UTC](https://forum.inductiveautomation.com/t/where-is-the-designer-log-viewer-diagnostics-info-stored/47632 "2021-06-10T02:07:42Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\ **Post date:** [June 10, 2021, 12:14pm UTC](https://forum.inductiveautomation.com/t/where-is-the-designer-log-viewer-diagnostics-info-stored/47632/2 "2021-06-10T12:14:51Z")
On vision and designer client side, you have to add a file apprender to collect logs > [@Add a RollingFileAppender for vision client logs to ease debug in client scope with external log viewer tools](http://forum.inductiveautomation.com/t/add-a-rollingfileappender-for-vision-client-logs-to-ease-debug-in-client-scope-with-external-log-viewer-tools/26659): > > Vision console is not very user friendly for logs analyse in CLIENT scope. So you can add a RollingFileAppender for all client’s logs produced with code like : logger = system.util.getLogger("myLogger") if logger.isDebugEnabled(): logger.debug("Hello, world!") (print message are not concerned and stay only in the console) In order to route the logs to others files in parallel with the vision console, you can add a call to startLogClient() in your client startup script. to stopLogClient() … As a side note, this New appender will not receive print, but only log.debug, info... --- _[View the full topic](https://forum.inductiveautomation.com/t/where-is-the-designer-log-viewer-diagnostics-info-stored/47632)._