# Alarm Historian Duplication

**URL:** <https://forum.inductiveautomation.com/t/alarm-historian-duplication/111068>\
**Category:** Ignition\
**Tags:** ignition81, vision\
**Created:** [September 29, 2025, 6:35pm UTC](https://forum.inductiveautomation.com/t/alarm-historian-duplication/111068 "2025-09-29T18:35:19Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dgratz](https://avatars.discourse-cdn.com/v4/letter/d/b19c9b/32.png) [@dgratz](https://forum.inductiveautomation.com/u/dgratz)\
**Post date:** [September 29, 2025, 6:35pm UTC](https://forum.inductiveautomation.com/t/alarm-historian-duplication/111068/1 "2025-09-29T18:35:19Z")

</div>

I have a database that records all the alarms in my Ignition gateway, which I’m planning to use in a different piece of software. I noticed today that every alarm entry is recorded twice, once with an eventtype of 1 and then again with 0. Since my alarms are all Boolean triggers, it makes sense that this is an “alarm active” and “alarm inactive” flag.

I want to know if there’s a way to suppress the second (“inactive”) entry. It’s unneeded in my application, and it’s just doubling the size of my database for no reason. Obviously, I know I can query the database to filter these results out; I’d just rather the storage space weren’t taken up at all, if that’s possible.

Is there an alarm setting that I missed that keeps from logging this second entry?

---

<div class="post-metadata">

**Author:** ![ryan.white](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryan.white/32/73193_2.png) [@ryan.white](https://forum.inductiveautomation.com/u/ryan.white)\
**Post date:** [September 29, 2025, 6:45pm UTC](https://forum.inductiveautomation.com/t/alarm-historian-duplication/111068/2 "2025-09-29T18:45:50Z")

</div>

Looking at how this field is used by the alarm system of Ignition, I doubt you can turn this off. This field is partially used in determining how long a configured alarm is in a specified state (Active, Inactive, Acknowledged), as well as providing a timestamp of when the state changed. This is one of the integral parts of the Alarm system of Ignition so disabling it would likely cripple said system.

> **[Alarming | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.1/platform/alarming#alarm-events-and-their-states)**
>
> Alarms are always configured on a Tag, excluding Vision client tags. Every time a Tag with a configured alarm receives an updated value, the configured alarm will examine the new value. If the new value on the Tag meets some criteria, as defined by...

> **[Ignition Database Table Reference | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.1/appendix/reference-pages/ignition-database-table-reference#alarm_events)**
>
> Ignition has a lot of systems built-in that will query the database automatically without requiring you to build a query. These systems automatically create the necessary tables in the database, insert the relevant data, and even query it back out...

---

<div class="post-metadata">

**Author:** ![dgratz](https://avatars.discourse-cdn.com/v4/letter/d/b19c9b/32.png) [@dgratz](https://forum.inductiveautomation.com/u/dgratz)\
**Post date:** [September 29, 2025, 6:58pm UTC](https://forum.inductiveautomation.com/t/alarm-historian-duplication/111068/3 "2025-09-29T18:58:09Z")

</div>

Ah alright. That’s helpful to understand; thank you!

I’ll just query the database with the extra condition.