# Igniton Edge - event-logging to database with store and forward?

**URL:** <https://forum.inductiveautomation.com/t/igniton-edge-event-logging-to-database-with-store-and-forward/110161>\
**Category:** Ignition\
**Created:** [August 25, 2025, 8:25pm UTC](https://forum.inductiveautomation.com/t/igniton-edge-event-logging-to-database-with-store-and-forward/110161 "2025-08-25T20:25:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jon\_Forbord](https://avatars.discourse-cdn.com/v4/letter/j/d9b06d/32.png) [@Jon\_Forbord](https://forum.inductiveautomation.com/u/Jon_Forbord)\
**Post date:** [August 25, 2025, 8:25pm UTC](https://forum.inductiveautomation.com/t/igniton-edge-event-logging-to-database-with-store-and-forward/110161/1 "2025-08-25T20:25:25Z")

</div>

We have a lot of events that originate on instances of Ignition Edge, and we populate some of these with additional context into database tables. Right now we do this on the main gateway using scripts and tag change events, but in cases of disconnect between the edge and the main gateway, the events are not captured by the tag change events. There is an option to set MQTT engine to fully process the events as we backfill from sparkplug B, but for several reasons this is not a good option for us. Are there any other mechanism we can use to have an event sourced at the edge, with some form of delivery guarantee from edge to a central database? Like an SQL bridge module extension for capturing events in Edge instances, with store and forward?

---

<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:** [August 25, 2025, 9:28pm UTC](https://forum.inductiveautomation.com/t/igniton-edge-event-logging-to-database-with-store-and-forward/110161/2 "2025-08-25T21:28:06Z")

</div>

You would have to roll your own cache in a persistent script variable, and forward with `system.util.sendRequest()` to the central gateway. Non-trivial, but you could use this topic for inspiration:

> [@Java concurrent queue for tag change scripts](https://forum.inductiveautomation.com/t/java-concurrent-queue-for-tag-change-scripts/82044):
>
> Continuing the discussion from [[SOLVED] Are tag Value Changed scripts running asynchronously?](https://forum.inductiveautomation.com/t/solved-are-tag-value-changed-scripts-running-asynchronously/68704/5): We've got code in our standard library that I need to log a value change on a tag and then associate various data points with that value change. The value is located in a UDT, and because this is part of our "standard" library we use for our customers, the number of tags is variable and quite possibly numerous so having a gateway tag event script isn't feasible for this solution. I was reading up on …