Issue with Generic Event Timestamp: Analyzing Recorded Video vs Live Notification
Answered
Hello,
I am developing an integration using the Network Optix Server API. My backend application consumes RTSP streams from past recordings (historical footage) to perform offline video analytics (specifically Face Recognition).When a face is detected, I send a Generic Event to Nx using /api/createEvent. I am currently facing a dilemma regarding the timestamp parameter and user experience:If I use the actual detection time (Past Timestamp):The event is correctly placed on the timeline. However, the notification in the Desktop Client appears deep down in the notification list (sorted chronologically). Operators often miss these alerts because they are not at the top of the list.If I use the current time (Current Timestamp):The notification appears at the very top of the list, ensuring the operator sees it. However, the thumbnail/snapshot shows the live feed (which is irrelevant), and clicking the notification takes the operator to the "live" moment instead of the actual evidence in the past.My Question:What is the recommended workflow/best practice for this scenario?I want to alert the operator immediately (top of the list) but ensure that clicking the event takes them to the correct moment in the past archive.
-
Hi Fatih,
The notification can be configured to have force acknowledgement. (Create bookmark as a mandatory “read receipt”), so the operator will always see it and need to “read” it for video/snapshot of the actual detection time.
Besides, Generic Event is a system event, it is not associated to any cameras naturally, so please remember to use cameraRef.
BTW, since the v6.1.0 has been released, and the API has been changed to POST /rest/v4/events/generic
Thanks.
0 -
Hi Ichiro,
Thank you for your response.0
Please sign in to leave a comment.
Comments
2 comments