Suggest an Idea

[priyankaraj]

Hello Product Management Team for Qlik Replicate,

We are requesting for your intervention in fixing the shortcoming / defect / bug within Qlik Replicate Latency Alert Notifications. 

Problem Statement: 

Email Message (field input) in Notifications is not independent between On / Off alerts that we are setting for Latency updates / alerts . For example, whatever we input or write in On Notifications duplicates in Off Notification for the "EMAIL MESSAGE" field. We firmly believe there's a defect, because this should be customizable as per our requirement and should not be uniform.  It's independent and editable as per requirements in "CONSOLE" and "EMAIL SUBJECT." 

We would appreciate if this capability can be enabled for "EMAIL MESSAGE." In Cummins, we have enabled Latency alert notifications and embedded a script in the email message to create a TICKET to our Production Support Team. While the the alerting mechanism is intact and working, we DO NOT WANT / REQUIRE a ticket to be created when latency resolves. Due to this defect / bug in the notifications for "EMAIL MESSAGE" Field, our Production Support Team @vishnu_valmikam / @MohnishVerma   is having to cancel hundreds and thousands of tickets. We would appreciate if this can be addressed on priority. 

Thank you.

Sharing a snippet for your review / view.

Sincere Regards,

Priyanka Raj

@Sairam_S @MerveKarakis @sw141 @Anonymous 

[dima_etkin]

Hi @priyankaraj 

The screenshot below taken from the windows Replicate V2021R11 provides the requested means to control the on and off messages.  

If you have configured a Replicate notification which does not behave as documented (sending different ON and OFF messages), please raise a support case for the issue to be reviewed. 

It is true that QEM has just a Latency above "N" time units as shown below:

Please clarify if you are asking to mimic the same behaviour in QEM notifications, as already available on Replicate. Please clarify in the comments.

Having said that, from the operational perspective, please consider adding a step to your automation, which  checks for existing new latency related tickets with a similar (or identical) header, and if so, skips creating a new ticket. 

Dima

[Nulee_Massaro]

Thank you for your comment. As this is a great suggestion, we will look into this request and see if there is any other demand for this enhancement. 

[Meghann_MacDonald]

From now on, please track this idea from the Ideation portal. 

Link to new idea

Meghann

NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you only see 1 tab with the login page, please try clicking this link first: Authenticate me! then try the link above again. Ensure pop-up blocker is off.