# Recommended Event Log

**URL:** <https://forum.inductiveautomation.com/t/recommended-event-log/112771>\
**Category:** Ignition\
**Tags:** ignition81, vision\
**Created:** [December 11, 2025, 7:54pm UTC](https://forum.inductiveautomation.com/t/recommended-event-log/112771 "2025-12-11T19:54:04Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![warren](https://avatars.discourse-cdn.com/v4/letter/w/97f17d/32.png) [@warren](https://forum.inductiveautomation.com/u/warren)\
**Post date:** [December 11, 2025, 7:54pm UTC](https://forum.inductiveautomation.com/t/recommended-event-log/112771/1 "2025-12-11T19:54:04Z")

</div>

On my vision client, I want to be able to monitor events that occur within the HMI. I have a separate screen handling all the alarms generated within the HMI, but I’d like to have another screen that will capture user actions. For example…

1. User-Defined events:
  1. Data modified within a cell. Could be detailed to before + after data, but really just a timestamp with the action, using a script within cellEdited
  2. Button pressed that initiates a sequence
  3. User role changes
  4. etc.

2. Machine triggered events:
  1. Sequence completion times

What type of table setup would I need to capture all of these. It would also be like writing to a console, using a system logger, but I need a friendly way for the operator, or tech support to go back through the machine history.

---

<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:** [December 11, 2025, 8:19pm UTC](https://forum.inductiveautomation.com/t/recommended-event-log/112771/2 "2025-12-11T20:19:30Z")

</div>

It is fairly typical to use a custom table with machine\_id, event\_id, and t\_stamp columns. Perhaps also operator\_id and operator\_notes columns.

With joinable tables for machine information and event descriptions.

Use named queries to retrieve with suitable filters. Display in tables and with my NoteChart module on plots. (Both Vision and Reporting charts.)

/shameless plug

---

<div class="post-metadata">

**Author:** ![warren](https://avatars.discourse-cdn.com/v4/letter/w/97f17d/32.png) [@warren](https://forum.inductiveautomation.com/u/warren)\
**Post date:** [December 11, 2025, 8:40pm UTC](https://forum.inductiveautomation.com/t/recommended-event-log/112771/3 "2025-12-11T20:40:49Z")

</div>

I see what you did there… I will definitely research more on that NoteChart, I can think of a few uses for this alone.

So your overall suggestion is to get this data into sql and query from a main table configured for whatever information desired beyond the basic (operator id, machine id, etc.)