Using CreateEvent API to generate the events but getting slow

Planned

Tanaya Ghosh

January 29, 2025 04:42 Edited

Hello,

I m using Create Event API to generate the events but the issue is the event which is getting genearted is been shown very slowly on the NX application ie,the person has shown the face and gone then the logs are getting captured and in that case the person is missing.

So,how to get the exact logs when the actual event has been occurred .Kindly help us to reach this.

The events which is getting captured are very slow.After the event occurence it is getting captured.

the image attached for reference. As you can see the person has gone then it is capturing.

0

• 

  Tanaya Ghosh

  January 29, 2025 04:41

  Hello Team,

  Please help me to resolve this issue.

  0
• 

  Ichiro

  • Network Optix team

  February 06, 2025 05:33

  Hi Tanaya Ghosh, 

  Thanks for your question. However, the provided information is kind of limited, making it difficult to conduct a proper investigation. To accurately provide the suggestions, it is suggested that a more detailed issue report is required.

  From the limited details available, it seems likely that the issue is timestamp-related.

  Specifically, the external system may be generating an event, but the camera’s video feed/mediaserver system time may not have a matching timestamp. Before proceeding, please verify whether the camera timestamp aligns with your access control or face detection system, as well as the external system and mediaserver.

   

  If you are using the API and have reviewed the documentation, you may already knew that timestamps can be assigned manually, ensuring alignment with actual event times. This synchronization is crucial before any troubleshooting.

  

  So, likely your next xteps:

  1.Verify timestamp synchronization between your environment, such as : access control system, camera, and mediaserver.

  2.Ensure that you have properly assigned timestamps when using the API if required.

   

  This is a fundamental procedure in system integration troubleshooting, and it may require further tests to isolate the exact mismatch. We kindly suggest that you develop a structured troubleshooting procedure to systematically identify the root cause and pinpoint the affected components more efficiently.

  This approach will help accelerate the investigation and resolution process.

  0

Please sign in to leave a comment.