How Do I Debug An Alert Not Being Sent?
The best place to check why an Alert was not executed is the Alert Engine log.
This can be found at:
*:\ARGENT\ArgentManagementConsole\ArgentAlertConsole\LOGS\AAC_ENGINE_LOG.TXT
Tue Jan 09 14:48:21.812 SEV1 User Alert EMAIL_GENERAL (E000008) is fired successfully. Argent Guardian Main Engine Is Back Online Thu Jan 11 08:40:22.387 SEV1 User Alert EMAIL_GENERAL (E000174) is fired successfully. Argent Guardian Main Engine Is Back Online Thu Jan 11 09:00:22.834 SEV1 User Alert EMAIL_GENERAL (E000188) is fired successfully. Service Print Spooler on node SEV1 is not running. Thu Jan 11 09:01:55.896 SEV1 User Alert EMAIL_GENERAL_CORRECTED failed to fire. Condition corrected for rule SVC_SPOOLER_W2K on SEV1. Re-check result: Rule 'SVC_SPOOLER_W2K' is no longer broken on server 'SEV1 (Spooler)'. Reset escalation. Orginal event: Service Print Spooler on node SEV1 is not running. Thu Jan 11 15:12:44.177 SEV1 User Alert EMAIL_GENERAL (E000189) is fired successfully. Argent Guardian Main Engine Is Back Online Thu Jan 11 15:14:25.253 SEV1 User Alert EMAIL_GENERAL (E000190) is fired successfully. Service Print Spooler on node SEV1 is not running. Thu Feb 22 16:37:44.653 SEV1 User Alert EMAIL_GENERAL (E000192) is fired successfully. URL Inaccessible
If you have attempted to fire an SMS Alert, you should also check the SMS_Debug_Log at:
*:\ARGENT\ArgentManagementConsole\ArgentAlertConsole\LOGS\SMS_DEBUG_LOG.TXT
12-Apr-2007 15:19:58.723: SMS Idevices released 12-Apr-2007 15:19:58.723: SMS MMI devices released 13-Apr-2007 09:21:21.438: SMS Idevices released 13-Apr-2007 09:21:21.453: SMS MMI devices released 16-Apr-2007 09:01:59.068: SMS Idevices released 16-Apr-2007 09:01:59.068: SMS MMI devices released