# Scripting to read gateway logs

**URL:** <https://forum.inductiveautomation.com/t/scripting-to-read-gateway-logs/64402>\
**Category:** Ignition\
**Tags:** scripting\
**Created:** [September 23, 2022, 4:30am UTC](https://forum.inductiveautomation.com/t/scripting-to-read-gateway-logs/64402 "2022-09-23T04:30:49Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![kgamble](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kgamble/32/8019_2.png) [@kgamble](https://forum.inductiveautomation.com/u/kgamble)\
**Post date:** [September 23, 2022, 5:12am UTC](https://forum.inductiveautomation.com/t/scripting-to-read-gateway-logs/64402/3 "2022-09-23T05:12:40Z")

</div>

> [@paul-griffith](#):
>
> The webpage just uses the system\_logs.idb file;

Ah, I started going the approach of hitting the `http://localhost/data/status/logs` endpoint, but was struggling with getting a `JSESSIONID`. Any ideas on how to get that with the builtin Ignition IDP enabled?

In regards to configuring logback, you can actually configure it to push straight into a database as well with a database appender. I am just looking for something to hit the internal logs directly through a project script.

Is there any reason you would say to go with the approach of parsing the wrapper log vs the logs endpoint? Other than the fact that's probably an implementation detail lol

---

_[View the full topic](https://forum.inductiveautomation.com/t/scripting-to-read-gateway-logs/64402)._