Date in the notiifcation

[suvbin]

Hi Qlik , 

Is there any way to insert date and time  for the latency reduced tickets? these tickets will generate when any of the task reduced the latency.

Right now we are getting the Notification (subject) like this  without date. 

Thanks in advance

[SachinB]

Hello @sub 

Thank you for reaching out to the Qlik community!

We do have only below listed supported notification variables. Please find the below link for the same.

https://help.qlik.com/en-US/replicate/May2023/Content/Global_Common/Content/SharedEMReplicate/Server...

The following variables are not supported even though they are available for selection: ACTIVE_TABLES, ERROR_TABLES , COMMAND, COMMAND_CODE, FULLLOAD_ERROR_TABLES, ERROR_CODE, SQL_STATEMENT, and COMMAND_PARAMETERS. 

You can look for the option you get an email in the inbox and consider that date and time.

Regards,

Sachin B.

[suvbin]

any other leads on this please.

[SushilKumar]

Hello Team,

As Sachin mentioned 

We do have only below listed supported notification variables. Please find the below link for the same.

https://help.qlik.com/en-US/replicate/May2023/Content/Global_Common/Content/SharedEMReplicate/Server...

how ever you recive the notification on Realtime basis and body also have server date as well.

Regards,

Sushil Kumar

[Heinvandenheuvel]

Hmm, is there not a date-time on the message envelope? 

Still, it would seem to be very reasonable to have the ability to include the date/time of the event.

I recommend an enhancement request.

Hein.

[suvbin]

yes there is no date and time in the subject of a ticket.  But  how the message is getting triggered as soon as the latency decrease ? I mean it will store some the latency column (with time and date) value  in postgresql right ? so how to take that value and then overwrite in the existing message ? Any clue please . 

Atleast till the enhancement been implemented, there should be some solution/workaround to customize the message right ? So could you please help with that

[suvbin]

where i have to post this ?

[john_wang]

Hello @suvbin ,

Totally agree with @Heinvandenheuvel :

Still, it would seem to be very reasonable to have the ability to include the date/time of the event.

I recommend an enhancement request.

---

In current versions there is no such variable available yet, Please raise a Feature Request in Ideation area.

Hope this helps.

Regards,

John.

[Heinvandenheuvel]

>>> yes there is no date and time in the subject of a ticket.

but the is the timestamp for the message itself, which should be close to the event tiemstamp?

>>>  I mean it will store some the latency column (with time and date) 

I suspect that for this kind of problem you are focusing on a relatively small set of task, perhaps for a few days or weeks until the core problem is understood. One way to get a bit of a handle on latency issues is to enable PERFORMANCE logging. Using that, you can create a script to select and present the latency from the task logs with 30 seconds granularity. I'll attach a PERL script to help parse the task log and present the PERFORMANCE trace into CSV for presentation.

You can also enable Replicate History for the selected tasks. From the manual:

"E.4 Replication history
The attrep_history table provides statistics about each task, such as the number and volume of records
processed during a particular timeslot. ... TIMESLOT_LATENCY int The latency at the end of the time slot. This is only applicable to CDC time slots. Note that this value contains the value of the target latency only.

Hein.