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

BAC Transaction alert time

Advisor

BAC Transaction alert time

 

Hi Team,

 

We have 2 Gateways and 2 DPS servers in our environment, wherein all the 4 servers are in the GMT+5:00 time zone in order to avoid data aggregation issues, as per below written in the HP Manual

 

Note:

All HP Business Availability Center servers, as well as the database servers,

must be installed in the same time zone, with the same daylight savings

time configuration, and be set to the same time.

HP Business Availability Center does not support setting the time zone for

its servers at a time zone that is on the half hour relative to GMT, for

example GMT+6:30 Indian. This may cause problems during data

aggregation, which is performed on the hour.

 

 

 

We have alerts configured in our environment wherein below is the alert definition

 

Whenever transaction fails, run opcmsg using below command since OM agent is installed on all the BAC servers

 

C:\Program Files\HP\HP BTO Software\bin\win64\OpC\opcmsg severity="<<Severity>>" a="<<Profile Name>>" o="BAC" msg_grp="BAC_Events" msg_text="Transaction <<Transaction Name>> of <<Profile Name>> for location <<Location Name>> has got failed at <<Transaction Time>>" 

 

 

We have appended transaction time parameter in the opcmsg custom message in order to know whether alert actions are triggered at the right time or not.

But in our case , whenever transaction fails, below is the message that we receive on OM console.

If we see here in the below message we can see that there is exactly half an hour difference, which is because of the time difference on the BAC server(GMT+5:00) and the current local time(GMT+5:30)

 

The first time (17:50:12) is the current local time(GMT+5:30) and the last time(5:17:44) is the BAC server time(GMT+5:00)

 

We wanted to know if  it is feasible to make the last time i.e. the opcmsg triggered time +30 minutes while the messages reaches OM console, without actually changing the BAC server time?

We need to check it’s feasibility since there is a lot of confusion in the application team since they consider by seeing these alerts as old ones or is reaching a bit delayed on console, which is actually not the case.

 

Major                    -------    17:50:12 12/23/13            <<server hostname>> <<app profile name>>         BAC_Events       BAC        Transaction <<transaction name>> of <<app profile name>> for location <<location name>> has got failed at Mon Dec 23 5:17:44 PM 2013 (Yekaterinburg Time) (+0500)   

 

Thanks & Regards

Lini

 

 

4 REPLIES
Acclaimed Contributor [Founder]

Re: BAC Transaction alert time (time zone)

[ Edited ]

>as per below written in the HP Manual

 

It seems this is a serious limitation that they all have to be the same and that they can't be on the half hour.

You may want to contact Support to ask for an enhancement in this area.

 

>for example GMT+6:30 Indian.

 

It seems strange that they didn't get this right. :-)  India should be GMT+5:30, with no DST.

And Venezuela would be another half hour example.

Re: BAC Transaction alert time

Hi Dennis,

 

Good Morning.

 

Does that mean right now it is not at all feasible to get the exact time appended to the BAC transaction alert message, because of the below constraint. Please confirm on the same.


Note:
All HP Business Availability Center servers, as well as the database servers,
must be installed in the same time zone, with the same daylight savings
time configuration, and be set to the same time.
HP Business Availability Center does not support setting the time zone for
its servers at a time zone that is on the half hour relative to GMT, for
example GMT+6:30 Indian. This may cause problems during data
aggregation, which is performed on the hour.

 

 

Thanks & Regards
Lini

Acclaimed Contributor [Founder]

Re: BAC Transaction alert time (time zone)

>right now it is not at all feasible to get the exact time appended to the BAC transaction alert message, because of the below constraint.

 

It sure seems like it.  You should contact Support to check to see if that limitation has been lifted and if not, to file an enhancement.

HPE Expert

Re: BAC Transaction alert time

Hi,

 

You might be able to implement a work-around by calling a batch file instead of opcmsg directly.

 

Send the arguments to the batch file, and inside the file add 30 minutes to the timestamp before calling opcmsg.

 

 

Eric Shaffer

"HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution."