Trigger one alert per failed message

[former_member210091]

Hey All,

We have configured alerts using ALRTCATDEF in our PI 7.11 system. The expiry time for alerts is 30 mins and the report RSALERTPROC runs every 1 Hr (to delete the expired alerts). We have several interfaces which run very frequently (some could run every 5-10 mins). We also have RSXMB_RESTART_MESSAGES running every 3 mins, this retries failed messages 10 times. Please also note that in alert rule, we have made sure that alerts are triggered only when there is a message ID. For e.g. if a sender FTP channel has some connectivity error, no messages/files will be polled hence we don't want alert e-mails. We have also tried to set "Max No of Dels" to 1 but that doesn't help either.

Below are the configurations we have tried:

1. Check "Multiple alerts of this rule" option in Alert Rule: When this option is checked, alert is triggered only for the first message failure, subsequent alerts are triggered only after the first alert is confirmed (by user) or the alert expires (due to RSALERTPROC). For e.g. if 2 messages failed within a span of 10 mins, only 1 alert e-mail is triggered. Mail for second interface is not triggered since we have checked "Multiple alerts of this rule" option. We don't want alerts for other message failures to stop.

2. Uncheck "Multiple alerts of this rule" option in Alert Rule: When this option is unchecked, alerts are triggered for each failure (and each retry). For e.g. if a message fails due to Message mapping error, we get 10 alert e-mails (for the same message), since RSXMB_RESTART_MESSAGES is running. We don't want to many alert e-mails for same message ID.

Now my question is, how can we configure alerts so that it only triggers 1 e-mail for each failure (one alert e-mail per message ID) but at the same time should not suppress alerts for other message ID's?

Thanks

Saif

Edited by: Saif Manzar on Feb 26, 2012 6:54 AM

[Former Member]

Hi,

in short: it is impossible. You will have to create your own alerting functionality here via a (preferably java) batch job.

Best Regards

Andreas

[former_member210091]

Andreas,

Thanks for your reply, i was hoping this should be a pretty standard requirement from SAP clients.

People want to get notified if a PI interface has failed.

They don't want several e-mails for the same error but at the same time, don't want to miss on any failed error messages too.

Thanks

Saif

[Former Member]

Saif,

Like you i am also surprised  to see that this is not part of std functionality. This is very simple & basic requirement.

PI should be smart enough not to send multiple alerts for same message ( which it is doing for checking the box) & still do not wait for confirmation. This should have been taken care but unfortunately not.

[Former Member]

Hi Saif,

As you said it should not trigger alerts. But basically, when a message gets failed it would try to reprocess the message.

When the message still fails even after reprocessing, then there should be an alert to notify that the message has failed.

This is the basic functionality. What do you think about this?

[Former Member]

Did you mange to solve this issue, BTW?

--Divyesh