# Read client logger data with an external tools

**URL:** <https://forum.inductiveautomation.com/t/read-client-logger-data-with-an-external-tools/9939>\
**Category:** Ignition\
**Created:** [April 21, 2015, 5:29pm UTC](https://forum.inductiveautomation.com/t/read-client-logger-data-with-an-external-tools/9939 "2015-04-21T17:29:29Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**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:** [July 18, 2019, 10:48am UTC](https://forum.inductiveautomation.com/t/read-client-logger-data-with-an-external-tools/9939/3 "2019-07-18T10:48:28Z")

</div>

could be a solution

> [@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() …

---

_[View the full topic](https://forum.inductiveautomation.com/t/read-client-logger-data-with-an-external-tools/9939)._