# Experimental Gateway logs viewer **URL:** \ **Category:** Module Development\ **Tags:** ignition83\ **Created:** [June 24, 2026, 11:27pm UTC](https://forum.inductiveautomation.com/t/experimental-gateway-logs-viewer/116143 "2026-06-24T23:27:27Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![David\_Stone](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/david_stone/32/79749_2.png) [@David\_Stone](https://forum.inductiveautomation.com/u/David_Stone)\ **Post date:** [June 24, 2026, 11:27pm UTC](https://forum.inductiveautomation.com/t/experimental-gateway-logs-viewer/116143/1 "2026-06-24T23:27:27Z")
I have been experimenting with mirroring the gateway logs on a designer window, I find the constant switching between windows and logout of the gateway webpage a pain when making and troubleshooting gateway scoped scripts, so I have experimented with this module, it adds a menu item in the Tools menu that opens a little gateway logs viewer window that mirrors the gateway logs. I am not sure if there is actually any people that will find this useful, but if you do, I may consider working further on the signed module to use on your dev servers. [Gateway-Logs.modl](https://github.com/system24seven/gateway-logs/releases/download/0.1.1/Gateway-Logs.modl) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/c/1/c14a36b6fe169ed75bdcc1aab3c9d3d0f4b39113.png) ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [June 24, 2026, 11:43pm UTC](https://forum.inductiveautomation.com/t/experimental-gateway-logs-viewer/116143/2 "2026-06-24T23:43:26Z")
What's the stack underlying it - direct HTTP calls to the REST API, or RPC, or push notifications, or something else? ---
**Author:** ![David\_Stone](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/david_stone/32/79749_2.png) [@David\_Stone](https://forum.inductiveautomation.com/u/David_Stone)\ **Post date:** [June 24, 2026, 11:56pm UTC](https://forum.inductiveautomation.com/t/experimental-gateway-logs-viewer/116143/3 "2026-06-24T23:56:47Z")
It's using the RPC, converting to some pretty basic JSON and sending them through to the designer. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [June 24, 2026, 11:57pm UTC](https://forum.inductiveautomation.com/t/experimental-gateway-logs-viewer/116143/4 "2026-06-24T23:57:52Z")
I use `tail -f .../wrapper.log` in an SSH window. Tough to beat it, as it doesn't rely on any Ignition functionality. ---
**Author:** ![David\_Stone](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/david_stone/32/79749_2.png) [@David\_Stone](https://forum.inductiveautomation.com/u/David_Stone)\ **Post date:** [June 24, 2026, 11:59pm UTC](https://forum.inductiveautomation.com/t/experimental-gateway-logs-viewer/116143/5 "2026-06-24T23:59:30Z")
Port 22 isn't allowed over most of the remote access platforms we do Ignition dev on unfortunately. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [June 25, 2026, 12:01am UTC](https://forum.inductiveautomation.com/t/experimental-gateway-logs-viewer/116143/6 "2026-06-25T00:01:05Z")
SSH can listen on multiple ports, not just 22. ---
**Author:** ![paul.longtine](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul.longtine/32/10599_2.png) [@paul.longtine](https://forum.inductiveautomation.com/u/paul.longtine)\ **Post date:** [June 25, 2026, 1:59pm UTC](https://forum.inductiveautomation.com/t/experimental-gateway-logs-viewer/116143/7 "2026-06-25T13:59:41Z")
Some see a direct SSH session as a "break-the-glass" operation, and then should only be used when absolutely necessary. Some deployment scenarios may also be containerized, where there may never be an option to expose a SSH server running in a container. In the latter option, though, you _should_ have the ability to tail logs from the container - just not through SSH - and even then, you would have to have a certain level of access to the infrastructure to view logs in the first place. These are certainly a fresh hell in some environments. The Designer already has its own database management tool, why not add in a log viewer to boot? ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [June 25, 2026, 2:15pm UTC](https://forum.inductiveautomation.com/t/experimental-gateway-logs-viewer/116143/8 "2026-06-25T14:15:17Z")
Not relying on Ignition functionality is key, IMNSHO. The wrapper log file (stdout from containers) includes information not found in Ignition's logging infrastructure, especially information about crashes and optional GC logging. And various non-logged gateway scoped prints, particularly those from native libraries. Comparing to the query tool in the designer is a category error. That tool operates on demand--it provides no asynchronous information about DB connections. I consider access to the wrapper log **essential** in a dev environment. ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [June 25, 2026, 2:51pm UTC](https://forum.inductiveautomation.com/t/experimental-gateway-logs-viewer/116143/9 "2026-06-25T14:51:58Z")
As long as we're going down this tangent (sorry, David) - has anyone ever experimented with the service wrapper's syslog output mechanism? > **[wrapper.syslog.facility Property - Java Service Wrapper](https://wrapper.tanukisoftware.com/doc/english/prop-syslog-facility.html)** This would be additional keys added to `ignition.conf`. ---
**Author:** ![tgarrison](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tgarrison/32/80965_2.png) [@tgarrison](https://forum.inductiveautomation.com/u/tgarrison)\ **Post date:** [June 26, 2026, 11:59am UTC](https://forum.inductiveautomation.com/t/experimental-gateway-logs-viewer/116143/10 "2026-06-26T11:59:56Z")
Great idea. Would love to give it a shot, as my biggest problem is closing the gateway webpage accidently.. and then having to go thru the process of getting back to the log. Having the log right there in designer would be fantastic. ---
**Author:** ![David\_Stone](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/david_stone/32/79749_2.png) [@David\_Stone](https://forum.inductiveautomation.com/u/David_Stone)\ **Post date:** [June 26, 2026, 12:27pm UTC](https://forum.inductiveautomation.com/t/experimental-gateway-logs-viewer/116143/11 "2026-06-26T12:27:48Z")
Module is linked in the first post.