# Recommended Event History

**URL:** <https://forum.inductiveautomation.com/t/recommended-event-history/117118>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [September 17, 2026, 4:01pm UTC](https://forum.inductiveautomation.com/t/recommended-event-history/117118 "2026-09-17T16:01:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Allison\_Manhard](https://avatars.discourse-cdn.com/v4/letter/a/bcef8e/32.png) [@Allison\_Manhard](https://forum.inductiveautomation.com/u/Allison_Manhard)\
**Post date:** [September 17, 2026, 4:01pm UTC](https://forum.inductiveautomation.com/t/recommended-event-history/117118/1 "2026-09-17T16:01:55Z")

</div>

Using Ignition 8.3. I'm not sure how ignition wants us to handle logging events, things like operator actions, breaker status change, other occurrences that can be important to have a record of happening, but are not necessarily alarms. I can set them all as alarms with diagnostic priority, but I don't find the resulting table to be particularly user friendly, although perhaps that could be fixed. I could also create a query that looks at a set of data and returns the value, but metadata isn't returned with it. It also seems unnecessarily complicated for what I would think is a common task. Is there a recommended way to handle events?

---

<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:** [September 17, 2026, 4:02pm UTC](https://forum.inductiveautomation.com/t/recommended-event-history/117118/2 "2026-09-17T16:02:45Z")

</div>

It sounds like you want the feature we call auditing:

> **[Enabling Auditing in a Project​ - Audit Log and Profiles | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.3/platform/audit-log-and-profiles#enabling-auditing-in-a-project)**
>
> Ignition's built-in auditing system automatically records certain actions that occur in the system, such as a Tag writes or User Source authentication, into a SQL database table. Utilizing the system involves creating an Audit Profile, followed by...