Detection Timeouts 


  • Symptom 

If anything registers above zero in this graph, it represents a failure to get through all the processes to send an event to telegram.


  • Possible Causes 

Slow internet connection on Site.

There are duplicate rules in the hub


  • Action required 

Determine if any action can be taken to improve internet connectivity.

Request a Buffer Limit increase. By Default the communication server offers a buffer of 10 events.
If the buffer fills and remains full for longer that the allotted timeframe to receive and transmit events, Detection Timeout will occur. Buffer can be increased from 10 – 100 on request.

If unresolved please register a support ticket.




Edge Predictions



  • Symptom 

No Predictions displayed on the graph.


  • Possible Causes 

Ame Hardware is Offline and not presenting metrics.

No options in configuration to predict, based on the Include tags.

Sensitivity Configuration to strict or no object detection to predict.

Ame Hardware not connected to DVR or NVR

Misconfiguration of RTSP Url , username or password.


  • Action required 

Is the device online and presenting other metrics like Online Status.

Check the configuration on the hub and adjust sensitivity.  

Check the FPS Metrics to confirm streams are being analysed.



Frames Per Second


  • Symptom 

FPS Below 4.50


  • Possible Causes 

Ame Hardware not connecting to the DVR/NVR.

Ame Hardware is locked out of the DVR/NVR due to invalid username and/or password.
Ame Hardware not detecting Iframes.

Too many channels or Stream configuration not within specification. ( High CPU Usage  )


  • Action required 

Confirm RTSP configuration on the hub , pay special attention to IP, Port, Username and Password.
Username and password cannot contain any special characters.

Set the FPS on DVR or NVR to 6FPS and Iframe or GOV to 3.

Resolution should be a maximum of 640 x 480 for 4 channels on BRT or 320 x 240 for 8 channels.


Test Signal 

  • Symptom 

No test signal


  • Possible Causes 

Test Signal is generated from the First process to the last and has no set value.

0 or N/A means the device is not sending tests


  • Action required 

Must be reported to your sales representative or by creating a support ticket.


ARMED / ONLINE STATUS


  • Symptom 

N/A

  • Possible Causes 

The Armed Status Value should always present a value of 0 or 1 .If the value is outside of this range an alert will be generated illustrating an Offline condition.


  • Action required 

Check the Scrape Duration metrics to assess if internet issues are being experienced.
Check the internet connection on site.

Log a support ticket with ISD.


CPU


  • Symptom 

Alerting due to High CPU Usage.


  • Possible Causes 

Cpu Should average below 80%.

If higher than 80% an Alert will be generated.


  • Action required 

Resolution May be too high  - Check DVR / NVR Configuration .

FPS or gov not set correctly – Check DVR / NVR Configuration.

Device overloaded or resource limitation – Check other metrics for any apparent issue.

log a support ticket for assistance.


INTERNET SCRAPE DURATION


  • Symptom 

Should be below 2 Seconds.

If higher than 2 Seconds an alert will be generated.


  • Possible Causes 

Slow Internet Connection.

Too many simultaneous Alerts. 

Device overloaded or resource limitation.


  • Action required 

Check DVR / NVR Configuration.
Troubleshoot other metrics.
Identify any anomalies in other metrics.
Log a support ticket for assistance.