# Edge to Front End Alarming **URL:** \ **Category:** Ignition\ **Tags:** perspective\ **Created:** [November 14, 2024, 2:05am UTC](https://forum.inductiveautomation.com/t/edge-to-front-end-alarming/98591 "2024-11-14T02:05:20Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![Eric\_White](https://avatars.discourse-cdn.com/v4/letter/e/85e7bf/32.png) [@Eric\_White](https://forum.inductiveautomation.com/u/Eric_White)\ **Post date:** [November 14, 2024, 2:05am UTC](https://forum.inductiveautomation.com/t/edge-to-front-end-alarming/98591/1 "2024-11-14T02:05:20Z")
I'm currently considering the alarm path for a scale out architecture and got stuck on a couple points. Not sure if I'm overthinking or overlooking something more simple so any pointers are always welcome. Current Setup: - Three-tiered architecture: 20x Edge Gateways \> Back End Gateway \> 2x Front End Gateways - Using MQTT between Edge and Back End - Edge Gateways are currently for data collection, but some will likely have perspective in the future. At the moment, I can see two possible alarm paths. 1. Edge-Based Alarms: - Configure alarms on edge gateway tags - Use remote tag providers to pass alarms across the network - Challenge: Each Front End would need a remote tag provider connection to each Edge. - Pro: Easier to manage - Con: May not scale well with many Front Ends and Edge Gateways - Con: Could complicate future edge-based Perspective implementations 1. Back End-Based Alarms: - Create alarms on Back End Gateway using reference tags from MQTT - Pro: More centralized approach - Con: May limit future edge-level Perspective deployments I think MQTT Alarms wouldn't be applicable for me as its not MQTT to the front end, and I have a hunch they are less flexible with alarm notifications?? (happy to be wrong on that though). ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/a/7ad1161bcbfe943e2302cb976df135063f54c8cb.png)