User Tools
Writing /app/www/public/data/meta/development/applications/alarmcache/purpose.meta failed
development:applications:alarmcache:purpose
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| development:applications:alarmcache:purpose [2017/07/18 09:49] – bcoffey | development:applications:alarmcache:purpose [2021/06/25 10:09] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | Author : Brian Coffey\\ | ||
| + | Date : 2017-07-18 | ||
| + | ==== The Need ==== | ||
| + | The alarm cache application was developed to essentially cache all the vital information about active alarms in the SNMP Manager which haven' | ||
| + | |||
| + | This functionality was used for the EMS 3.1 release which includes indoor mapping and section colouring for indoor venues (such as AT&T Stadium). Before alarm cache was implemented the EMS Cache handled all caching of data, this included everything present in the SNMP Manager DB and hence was heavily tied to the current domain structure and meant scalability and maintainability was an issue going forward. | ||
| + | |||
| + | Since the alarm cache contains the vital data on alarms, we can query its DB on a cluster, carrier or section level returning alarms instantly to the EMS | ||