# 2 gateway... How to ack alarms from

**URL:** <https://forum.inductiveautomation.com/t/2-gateway-how-to-ack-alarms-from/6728>\
**Category:** Ignition\
**Created:** [June 18, 2013, 10:23pm UTC](https://forum.inductiveautomation.com/t/2-gateway-how-to-ack-alarms-from/6728 "2013-06-18T22:23:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![gnguyen](https://avatars.discourse-cdn.com/v4/letter/g/41988e/32.png) [@gnguyen](https://forum.inductiveautomation.com/u/gnguyen)\
**Post date:** [June 18, 2013, 10:23pm UTC](https://forum.inductiveautomation.com/t/2-gateway-how-to-ack-alarms-from/6728/1 "2013-06-18T22:23:33Z")

</div>

Imagine two independent system. But we need to ack alarm on both side from any client. How can we handle this…

---

<div class="post-metadata">

**Author:** ![greg.simpson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/greg.simpson/32/3135_2.png) [@greg.simpson](https://forum.inductiveautomation.com/u/greg.simpson)\
**Post date:** [July 12, 2013, 6:12pm UTC](https://forum.inductiveautomation.com/t/2-gateway-how-to-ack-alarms-from/6728/2 "2013-07-12T18:12:58Z")

</div>

This is pretty tough and there isn’t going to be a good way to do it. You could run queries against the database to see the alarms and acknowledge them, however, this probably wont have any affect on the pipelines.

The other suggestion would be to create a custom module that exposes a servlet to acknowledge alarms.