# Webdev Request Debug Screen

**URL:** <https://forum.inductiveautomation.com/t/webdev-request-debug-screen/61029>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [June 21, 2022, 6:38pm UTC](https://forum.inductiveautomation.com/t/webdev-request-debug-screen/61029 "2022-06-21T18:38:33Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![kyler.kamyszek](https://avatars.discourse-cdn.com/v4/letter/k/a4c791/32.png) [@kyler.kamyszek](https://forum.inductiveautomation.com/u/kyler.kamyszek)\
**Post date:** [June 21, 2022, 6:38pm UTC](https://forum.inductiveautomation.com/t/webdev-request-debug-screen/61029/1 "2022-06-21T18:38:33Z")

</div>

I’m looking to create a debug/status screen for my WebDev module.

I have an application that posts to webdev when I get a status update from a robot. If something happens ot I give the application a response with an error status, the application continues to send the same data. I want to display the incoming requests in a FIFO of some kind and possibly track to see if it’s a retry message (if the application doesn’t already do it).

I’m thinking about just using a db table to hold the data, but was curious if someone had a better idea.

Is there another way to store global (gateway) data other than a db table or tag?

---

<div class="post-metadata">

**Author:** ![Mikhail\_Simin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mikhail_simin/32/35931_2.png) [@Mikhail\_Simin](https://forum.inductiveautomation.com/u/Mikhail_Simin)\
**Post date:** [June 22, 2022, 5:27pm UTC](https://forum.inductiveautomation.com/t/webdev-request-debug-screen/61029/2 "2022-06-22T17:27:52Z")

</div>

If you are trying to keep track of incoming requests, there are a few ways to achieve this. You can either use a database table, a dataset tag, or a tag with history enabled to record the data coming in. This will allow for the data to be shared and visible by all the projects running on that gateway.

---

<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:** [June 22, 2022, 5:59pm UTC](https://forum.inductiveautomation.com/t/webdev-request-debug-screen/61029/3 "2022-06-22T17:59:25Z")

</div>

If you don’t care about persistence outside of the lifetime of your gateway, you could use `system.util.getGlobals()`. Just be careful if you store any custom class instances, as it can be a source of memory leaks; built-in Python data structures are fine.

---

<div class="post-metadata">

**Author:** ![kyler.kamyszek](https://avatars.discourse-cdn.com/v4/letter/k/a4c791/32.png) [@kyler.kamyszek](https://forum.inductiveautomation.com/u/kyler.kamyszek)\
**Post date:** [June 22, 2022, 6:10pm UTC](https://forum.inductiveautomation.com/t/webdev-request-debug-screen/61029/4 "2022-06-22T18:10:30Z")

</div>

Thank you both.

I’m going to go down the system.util.getGlobals() route first, then try a dataset tag.