Application Perf Mgmt (BAC / BSM) Support and News Forum
Showing results for 
Search instead for 
Do you mean 

Event Based Alert - Actions Log

Highlighted
Frequent Advisor

Event Based Alert - Actions Log

Hi All, 

 

for each transition I have event based alerts with a follow up alert (both run executable file as action). Since the upgrade from BAC 8.07 to BSM 9.23 I receive sometimes the "ok" before the "fail" and the events still remain "open" in our BCM Umbrella CMDB System to which BMS is connected.

See this example. This is one alert log and the "ok" comes 1 minute after the "fail":

 

Log.jpg

 

But this is the time we receive the action (msend) of this alert:

14:05:40 OK

14:05:42 Fail

 

Is there another log where I can see exactly when BSM executes the alert action?

 

Thanks and kind regards!

3 REPLIES
HPE Expert

Re: Event Based Alert - Actions Log

Try "alerts.ejb.log" on the DPS, ..:\HPBSM\log\alerts
Frequent Advisor

Re: Event Based Alert - Actions Log

Hi PatWest and thanks for the reply. 

 

I found it exactly where you said. 

 

 

The "ok" seems to been started and executed before the related "fail" even if the the agent sent the "fail" before (see my previous alert log screenshot). 

I am not really a Log specialist, but I post the logs of these actions anyway, maybe someone has an idea:

 

2014-03-25 14:05:40,315 [pool-AlertMDBContext-thread-1636] (AlertHandler.java:114) INFO - System is not in staging mode

2014-03-25 14:05:40,410 [pool-AlertMDBContext-thread-1636] (AlertHandler.java:418) INFO - Alert (id: 1dcc909d23028b31766285d433d0addf, customer id: 1, name: BEM_Transaction fail) was sent successfully
2014-03-25 14:05:40,530 [pool-AlertMDBContext-thread-1636] (AlertHandler.java:114) INFO - System is not in staging mode
2014-03-25 14:05:40,643 [pool-AlertMDBContext-thread-1636] (AlertHandler.java:418) INFO - Alert (id: 1dcc909d23028b31766285d433d0addf, customer id: 1, name: BEM_Transaction fail) was sent sucessfully
2014-03-25 14:05:40,927 [pool-NotificationMDBContext-thread-249] (ExecutableNotification.java:103) INFO - Executable ended successfully (alert id: 1dcc909d23028b31766285d433d0addf). Command line: d:\hpbsm\tools\msend\bin\msend -n BEM -j d:\hpbsm\tools\msend -a BAC_EV -m "Tue Mar 25 2:05:27 PM 2014 [Central European Time] [+0100] | USP_application | BEM_Transaction fail | Administration | USP_3MK | ACONET_1 | Informational | N/A | Transaction OK", exit code: 0
2014-03-25 14:05:40,928 [pool-NotificationMDBContext-thread-249] (NotificationTask.java:197) INFO - Notification (type: Executable, alert id: 1dcc909d23028b31766285d433d0addf command: d:\hpbsm\tools\msend\bin\msend -n BEM -j d:\hpbsm\tools\msend -a BAC_EV -m "Tue Mar 25 2:05:27 PM 2014 [Central European Time] [+0100] | USP_application | BEM_Transaction fail | Administration | USP_3MK | ACONET_1 | Informational | N/A | Transaction OK") was executed successfully
2014-03-25 14:05:40,931 [pool-NotificationMDBContext-thread-249] (TimeBasedCacheImpl.java:95) INFO - Refreshing the cache
2014-03-25 14:05:42,527 [pool-NotificationMDBContext-thread-246] (ExecutableNotification.java:103) INFO - Executable ended successfully (alert id: 1dcc909d23028b31766285d433d0addf). Command line: d:\hpbsm\tools\msend\bin\msend -n BEM -j d:\hpbsm\tools\msend -a BAC_EV -m "Tue Mar 25 2:04:14 PM 2014 [Central European Time] [+0100] | USP_application | BEM_Transaction fail | Administration | USP_3MK | ACONET_1 | Minor | 1.Action.c[154]: Error: 04: Fehler bei Aufruf Administrations Link | Transaction failed", exit code: 0
2014-03-25 14:05:42,527 [pool-NotificationMDBContext-thread-246] (NotificationTask.java:197) INFO - Notification (type: Executable, alert id: 1dcc909d23028b31766285d433d0addf command: d:\hpbsm\tools\msend\bin\msend -n BEM -j d:\hpbsm\tools\msend -a BAC_EV -m "Tue Mar 25 2:04:14 PM 2014 [Central European Time] [+0100] | USP_application | BEM_Transaction fail | Administration | USP_3MK | ACONET_1 | Minor | 1.Action.c[154]: Error: 04: Fehler bei Aufruf Administrations Link | Transaction failed") was executed successfully

 

 

 

Thanks and kind regards!

HPE Expert

Re: Event Based Alert - Actions Log

Set the alerts log level to DEBUG , to get more information in this log.

 

On the DPS , make a copy first of this file, then edit it ..:\HPBSM\conf\core\Tools\log4j\EJB\alerts.properties

 

and change the lines:

 

alerts.loglevel=DEBUG

def.file.max.size=5000KB
def.files.backup.count=10

 

Now wait till the problem happens. There will be more information now in ALERTS.EJB.LOG

 

good luck,

PatW