Internal Errigal Collaboration Wiki

User Tools

Site Tools

Trace: • res-p9126 • res-p9114
Writing /app/www/public/data/meta/onboarding/snmpmanager/auto-ticket_creation_from_alarms.meta failed
onboarding:snmpmanager:auto-ticket_creation_from_alarms

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
onboarding:snmpmanager:auto-ticket_creation_from_alarms [2017/02/17 19:56] – dmcgeeonboarding:snmpmanager:auto-ticket_creation_from_alarms [2021/06/25 10:09] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== Auto-ticket creation from alarms ======
 +
 +Author: David McGee
 +
 +**Introduction**
 +
 +It is important to note that one of the popular functions of the IDMS platform is automatic ticket generation, from incoming alarms. Varying trap rules are in place to create tickets automatically from alarms that do not clear themselves in a certain period of time. This can vary by vendor, severity and equipment type. Rules have been fine-tuned over the last decade or so on some of our customers' systems to create a good baseline. 
 +
 +The SNMP Manager interacts with the Ticketer application in order to automatically create tickets from incoming alarms based on service level agreement timeframes set our by our customers. This is often based on alarm severity: Critical, Major, Minor, Warning, etc. Tickets do not create for 'Informational' or cosmetic alarms from telecoms systems, by default. 
 +
 +**Relevant Domains/Database Tables**
 +
 +__SNMP Manager__
 +
 +  * NetworkElement
 +  * ActiveAlarm
 +  * RemoteTicket
 +  * TrapRule
 +
 +__Ticketer__
 +
 +  * Ticket
 +
 +**Class Diagram**
 +
 +Check out the class diagram below, and let a colleague know if you have any questions regarding this process! Feel free to get in touch with myself (Dave), also! 
 +
 +{{:onboarding:snmpmanager:remoteticketclassdiagram.png|}}
 +
 +**Trap Rules - Automatic Ticket Creation Examples**
 +
 +The logic for triggering ticket creation based on incoming alarms can be customised in a trap rule for a specific vendor/equipment type. Our trap rules are written in Groovy. Please see some screenshots of the important pieces of these rules, in relation to automatic ticket creation.
 +
 +__ADC/TE Spectrum__ 
 +
 +{{:onboarding:snmpmanager:adc_te_spectrum_example.png|}}
 +
 +__SOLID__ 
 +
 +{{:onboarding:snmpmanager:solid_example.png|}}
 +
 +__TEKO__
 +
 +{{:onboarding:snmpmanager:teko_example.png|}}
 +
 +__Internal Errigal Watchdog__ 
 +
 +{{:onboarding:snmpmanager:internal_errigal_watchdog_example.png|}}
 +
 +The ticketCreationDelay values are set in seconds. As you can see, there are similarities between the rules shown. Sometimes this depends on the customer's expectations. Increasing the ticketCreationDelay timeframes can result in a less noisy Ticketer environment for NOC engineers to work through. However, the right balance must be found to enable fast responses with telecoms equipment issues that need to be resolved quickly. You can see that internal errigal watchdog alarms generate tickets from alarms immediately! (0 value)
 +
 +**Self-assessment questions**
 +
 +On a QA environment:
 +
 +  - Try find out how many remote tickets exist on the SNMP Manager database?
 +  - How many tickets exist on the ticketer database?
 +  - Briefly ask a colleague about manual ticket generation. How does this compare to automatic ticket creation?
 +  - How many remote tickets exist for active alarms that are still active? (cleared=false)
 +  - Are there many active alarms (that are still cleared=false) that do not have remote tickets? (Could indicate an issue, or could relate to the alarm severity - there may not be an issue!)
 +
  

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki