# Alarm Pipeline Validation

**URL:** <https://forum.inductiveautomation.com/t/alarm-pipeline-validation/15720>\
**Category:** Ignition\
**Created:** [October 19, 2017, 7:29pm UTC](https://forum.inductiveautomation.com/t/alarm-pipeline-validation/15720 "2017-10-19T19:29:49Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![namesdontmatter](https://avatars.discourse-cdn.com/v4/letter/n/bc79bd/32.png) [@namesdontmatter](https://forum.inductiveautomation.com/u/namesdontmatter)\
**Post date:** [October 19, 2017, 7:29pm UTC](https://forum.inductiveautomation.com/t/alarm-pipeline-validation/15720/1 "2017-10-19T19:29:49Z")

</div>

We have a number of Ignition servers, each one with their own Alarm Pipelines.

I’d like to create a way that will allow Server A to send an email to Server B once every 30 minutes, and if Server B doesn’t get the email, Server B notifies everyone that something is wrong with Server A’s pipeline or Ignition Gateway.

Similarly, Server B will send an email to Server A once every 30 minutes. If Server A doesn’t get the email, then everyone is notified.

Ultimately, I just want to have each of the servers watching eachothers’ backs so that if a pipeline gets disabled or a server is unable to reach the email server, then we’ll know right away.

Does anyone know a good place to start for something like this?

Thanks!