DX Infrastructure Management

Expand all | Collapse all

Is it possible to trace back an email to a specific alarm?

  • 1.  Is it possible to trace back an email to a specific alarm?

    Posted 09-21-2018 02:24 PM

    We have been looking at the NAS_TRANSACTION_LOG in the UIM DB and the NAS_TRANSACTION_LOG that is a small sqliteDB in the nas probe folder to try to come up with a relationship map so that we can trace back a specific email to an alarm. There does not seem to be any fields to create a relationship between the two.

     

    Has anyone else tried to do this? Doing this helps us see the complete life cycle of an alarm from start to finish. Has anyone come up with a way to do this?



  • 2.  Re: Is it possible to trace back an email to a specific alarm?

    Posted 09-24-2018 09:15 AM

    this is not stored in the nas databases.

    You could look for the email action but this will probably not provide you with what you are looking for as this only provides that a NIMBUS message with an email subject was sent.

    Nothing really about what happened after that.

     

    The only way to see the relationship between a particular alarm and the actual email would be to capture the information from the emailgtw probe logs on loglevel 3 or higher.

    there you can see the alarmid along with the information about the sender etc and if the email was successful.

    None of this detail is relayed back to the nas probe or stored any place.



  • 3.  Re: Is it possible to trace back an email to a specific alarm?

    Posted 09-24-2018 09:25 AM

    nimid should be the value that ties the two together though the contents of nas_transaction_log tables in the two locations should be similar. And nas_transaction_log shouldn't contain information about the AO that generated the email.

     

    Looking at the schema at the end of https://c.na53.content.force.com/servlet/fileField?id=0BE60000000PBnT  it looks like you want to query nas_activity_log but there's really nothing useful in what's recorded within that table to tie it back to the triggering alarm.

     

    Probably what you'd need to do is to generate and send the email via a script and then you'd be able to record whatever information you needed for tracking purposes as part of the script.