# Gateway Process Guardian

**URL:** <https://forum.inductiveautomation.com/t/gateway-process-guardian/68956>\
**Category:** Ignition\
**Created:** [January 24, 2023, 10:20am UTC](https://forum.inductiveautomation.com/t/gateway-process-guardian/68956 "2023-01-24T10:20:28Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![thidalgo](https://avatars.discourse-cdn.com/v4/letter/t/898d66/32.png) [@thidalgo](https://forum.inductiveautomation.com/u/thidalgo)\
**Post date:** [January 24, 2023, 10:20am UTC](https://forum.inductiveautomation.com/t/gateway-process-guardian/68956/1 "2023-01-24T10:20:28Z")

</div>

Hi, I'm looking for a solution for monitoring the Gateway process and its underlying java runtime (Zulu Platform x64 architecture) so that in case of failure, the tool could restart the Gateway. Something like this: [Automatically Restart Crashed Or Hanged Applications | W-Shadow.com](https://w-shadow.com/blog/2009/03/04/restart-on-crash/) but native in the OS or a more official or professional tool with the ability to identify more precisely the process to monitor. Kind regards.

---

<div class="post-metadata">

**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:** [January 24, 2023, 4:22pm UTC](https://forum.inductiveautomation.com/t/gateway-process-guardian/68956/2 "2023-01-24T16:22:53Z")

</div>

The actual Java process that runs the Ignition gateway is _already_ managed by a 'service wrapper' - specifically Tanuki's: [What is the Java Service Wrapper? - Java Service Wrapper](https://wrapper.tanukisoftware.com/doc/english/introduction.html)

The `ignition.conf` file is directly configuring the service wrapper. You will probably find a lot of the options you want in the documentation for the service wrapper.

Ignition specific service configuration is available here, although it's less management-of-the-process focused (since the wrapper handles most of that for us):  
[https://docs.inductiveautomation.com/display/DOC81/Gateway+Configuration+File+Reference](https://docs.inductiveautomation.com/display/DOC81/Gateway+Configuration+File+Reference)

---

<div class="post-metadata">

**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:** [January 24, 2023, 4:42pm UTC](https://forum.inductiveautomation.com/t/gateway-process-guardian/68956/3 "2023-01-24T16:42:40Z")

</div>

The Ignition gateway implements two generic endpoints for monitoring that should be easy to pull into common web-monitoring frameworks:

- `http://someGateway/StatusPing` as JSON

- `http://someGateway/system/gwinfo` as semicolon-delimited key-value pairs.

The former is super simple. The latter is more informative. Either could easily be incorporated in a large monitoring platform.

---

<div class="post-metadata">

**Author:** ![thidalgo](https://avatars.discourse-cdn.com/v4/letter/t/898d66/32.png) [@thidalgo](https://forum.inductiveautomation.com/u/thidalgo)\
**Post date:** [January 25, 2023, 7:44am UTC](https://forum.inductiveautomation.com/t/gateway-process-guardian/68956/4 "2023-01-25T07:44:29Z")

</div>

Very interesting information, let me check it, thanks.
