=====Sub Case Reason N/A=====

**Level:**   
  *  - __Major__ 

**Purpose:** Here and there, there are going to traps that don't have a reason value assigned for the Ticketer Integration. This checks the logs for that because ATC get annoyed by it and may send a ticket. 

**Scenario:** <code>subCaseReason=N/A</code> was found in the logs of Ticketer Integration, found at ~/logs/spring-boot/ticketer-integration.log. 
On only atcapps1.atc

**Resolution:** 
If there isn't a ticket/case with an N/A reason logged in the last hour.

**Manual Action Steps:** 
  - Please note this is a temporary alarm until Feb 2022 when we add a default option to the traps.
  - First you will have to find the trap that caused this. 
  - SSH to the server. <code bash> ssh scotty@atcapps1.atc </code>
    - Pry into the Ticketer Integration logs. <code>vim logs/spring-boot/ticketer-integration.logs</code>
        - Press ''/'' and then <code>subCaseReason=N\/A</code>
        - Copy the name of the trap that cause this greivance. 
    - Alternatively you can check moros.err:5601/app/kibana and search the Ticketer Intergration logs for <code>subCaseReason=N/A</code>
  - With the name of the trap in clipboard, head over to the trapReasonMapping.csv
    - <code>sudo vim /var/spring-boot/ticketer-integration/trapReasonMapping.csv</code>
    - Have a quick search round the file. Use / and Ctrl/Cmd+Shift+V. The trap name should be missing.
    - Try to keep the list reasonably alphabetically sorted. Add the trap's name into the file along with the reason "Active Failure". There are many examples in the list for formatting.
  - There might be an ATC ticket if they added one. If there is update it. Consult with others if you want to tell ATC we detected a problem and added a fix. 
        


**Auto Clear:** Likely it will without you doing anything.
Follow this guide and fix the problem or it will happen again and ATC will message us. 

**Note:** There is an OpsDev to make this redundent soon.