Setting up custom logging for auto-ticketing activity from the CASDgtw

Discussion created by 1_hdoan on Mar 15, 2012

Does anyone know how to setup custom logging for whenever the CASDgtw sends a request to CASD to open a ticket?


This activity log would contain the:

1) date of ticketing request

2) ticket number that was assigned for the alarm that generated the ticket

3) alarm message itself

5) a bunch of custom fields ($custom_2, $custom_3, $custom_5, etc ) that are populated in the alarm.  These custom field are populated using the alarm enrichment probe and reflect the associated application, hostname, and knowledge-base number for the alarm being raised.