http://3.86.49.49/ 2026-04-17T14:33:09+00:00 http://3.86.49.49/ http://3.86.49.49/lib/tpl/docnavwiki/images/favicon.ico text/html 2021-06-25T10:09:56+00:00 Anonymous (anonymous@undisclosed.example.com) http://3.86.49.49/doku.php?id=development:applications:alarmcache:configuration&rev=1624612196&do=diff Alarm Cache Configuration File The config file is located at /usr/local/grails/AlarmCacheConfig.groovy RabbitMQ Configuration rabbitmq { enabled = true credentials { username = 'rabbit_ems' password = '#rabbit321!#' host = 'qaextlb1' virtualHost = 'ems' } queues { //Incoming Message alarmCacheQueue = 'alarm_cache_inbound_queue' //Outgoing Message } exchanges { //Incoming Message snmpAuditEventExchange = 'snmp_manager_audit_event_exchange_topic'… text/html 2021-06-25T10:09:56+00:00 Anonymous (anonymous@undisclosed.example.com) http://3.86.49.49/doku.php?id=development:applications:alarmcache:domains&rev=1624612196&do=diff Author : Brian Coffey Date : 2017-07-18 Alarm Cache Domains ActiveAlarm The purpose of this domain is to store all active alarms present in the SNMP Manager DB that are not cleared, once they clear in the SNMP Manager, they will be deleted from the alarm cache DB. text/html 2021-06-25T10:09:56+00:00 Anonymous (anonymous@undisclosed.example.com) http://3.86.49.49/doku.php?id=development:applications:alarmcache:howto&rev=1624612196&do=diff Alarm Cache How Tos * Shutdown and Startup text/html 2021-06-25T10:09:56+00:00 Anonymous (anonymous@undisclosed.example.com) http://3.86.49.49/doku.php?id=development:applications:alarmcache:purpose&rev=1624612196&do=diff 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't cleared, namely their carrier, cluster and section information. text/html 2021-06-25T10:09:56+00:00 Anonymous (anonymous@undisclosed.example.com) http://3.86.49.49/doku.php?id=development:applications:alarmcache:restapi&rev=1624612196&do=diff Alarm Cache REST API --- Colm Carew 2017/07/20 02:14 The V1 REST API of Alarm Cache has 2 Urls, 1 for obtaining your JSON Web Token and 1 for obtaining alarms /api/login This is the URL for obtaining the authorisation web token and it only accepts a POST text/html 2021-07-21T17:05:17+00:00 Anonymous (anonymous@undisclosed.example.com) http://3.86.49.49/doku.php?id=development:applications:alarmcache:troubleshooting&rev=1626883517&do=diff Troubleshooting Alarm Cache Sync Up Alarms At any given time the following two queries should match in count: select count(*) from alarm_cache.active_alarm; select count(*) from snmp_manager.active_alarm where !cleared; If a restart is ever required, running the above 2 queries is recommended to ensure everything is still synced up, it should be since any messages received will wait on the queue until the application is back up. If these do not match something has gone wrong with the proce… text/html 2021-06-25T10:09:56+00:00 Anonymous (anonymous@undisclosed.example.com) http://3.86.49.49/doku.php?id=development:applications:alarmcache:works&rev=1624612196&do=diff Author: Brian Coffey Date: 2017-07-18 High Level Operation SNMP Manager Similar to how the ticketer works with eBonding, the SNMP Manager is set to 'listen' on certain domains in the database for changes (inserts, updates and deletes). Different domains can be listened to for different changes. Currently for 3.1 the following are the domains listened on: