This article explains best practices for creating a support request on SAFR support portal.


Two methods to file a ticket

  1. Email
  2. Web Form


Regardless of how you file a ticket, the same information should be provided.  Below describes information needed to resolve your issues most efficiently.


Web Form Submission

1. Sign into the SAFR Support Portal at https://support.safr.com/

2. Click "New Support Ticket"


3. Enter subject line.

Subject should be short concise statement that clearly summarizes the issue or concern.


4. Select the Request Type

Depending on the Request Type selected, different fields will appear.  The following sections describe each type.


General Question

For general question, fill in your question in the Description field.

Suggestion

If suggestion, select the choice in the provided dropdown that best describes what the suggestion is about and enter your comments in the Description field.

Cloud Outage

Select Cloud Outage only if SAFR Cloud is unavailable or you are unable to log in.  If you are facing a problem with a specific feature, please chose Technical Support option.


If you select Cloud outage, enter responses to the two questions and provide a Description of the issue in the Description field.  


Make sure to provide enough information to help our team identity and resolve the issue quickly:

  • Location you were accessing SAFR from
  • Browser and operating system you were using or SAFR Application
  • Screenshot or text of errors that you observed

Technical Support

For technical support issues, you will be asked to fill out the following fields.


How does this impact your businessThis field lets the support team know the priority that should be given to the issue.  Please chose carefully using the descriptions on each option as a guide.

Product, Version and Platform

Provide the product, version and platforms that you are experiencing the issue on.  If more than one, add those to the description.

Steps to reproduce

Provide a clear an consist list of steps that you followed when you encountered the issue.  Please start from launching the application because sometimes issues only occur if done in a certain order.

Expected result

Explain what you expected the application to do.

Actual result

Describe what the application did.

Description

Add any more details that will help the support engineer to understand your issue and how to resolve.  
  • Your overall objective (this will help us identify alternate solutions or possible workarounds)
  • Information about the system specs and its current load
  • Any related details that may help explain or give insight into root case


You can also upload files or images that will help to understand the issue.


After submitting your ticket, you will receive an email confirming receipt.  Responses to your ticket will go to the same email conversation.  You can also post updates to your ticket directly through the support portal.  You can find your ticket in the Tickets page of the support portal.


Email Submission

As a convenience, you have the option to submit a new support request via email.  You will receive a response back 


Important: Even when submitting a ticket through email, it is very important you provide the same information.  In general its preferable to submit your initial ticket through the Web Form to allow automations to quickly pre-process and route your tickets to the right people.


Examples

Please refer to the following examples for how to submit a proper ticket and what information to provide for fastest processing.


Server

SubjectAfter upgrading from 3.5 to version 3.8 Images are not appearing in clients and SAFR object storage service is highlighted in red in server status.bat

Product

SAFR Server / 3.8 / Windows Server 2019

Steps to repro

With 3.5 installed
Create backup of system
Run 3.8 installer
Upon completion, open SAFR Desktop
Observe images are not present in Events viewer
Run check.bat and observe status for CVOS is red

Expected result

CVOS should start and images shown as normal

Actual result

No images and cvos is in red status in check.bat

Description

Previous version: 3.5.136
Version updated to: 3.8.141

After upgrade we observed that images no longer were appearing in events window on SAFR Desktop. We also tried SAFR Web Console and observed the same.

Below is output from check.bat:
<screenshot of output from check.bat script>

Attached is output from syscollect.bat and contents of the install.log file.
Attachmentssyscollect.tar.gz (get this by running syscollect.bat in bin directory)
install.log (located in c:\Program Files\RealNetworks directory)


SAFR Desktop Application

SubjectVideo Feeds report low DPS on feeds after a few days of operation

Product

SAFR Desktop / 3.5 / Windows 10

Steps to repro

Start SAFR Desktop with folkowing feeds:
<screenshot of feeds from Edit Processor Config window so all properties are shown>

Observe DPS is same as FPS at start.
Let it run a few days
Observe DPS is lower than FPS

Expected result

DPS remains at levels as when it was started

Actual result

DPS becomes lower than expected for server capacity

Description

Screenshot of Video feeds window when started (showing starting DPS):
<screenshot>
Screenshot of Video feeds window when DPS is low (showing low DPS):
<screenshot>
Attachmentssyscollect.tar.gz (get this by running syscollect.bat in bin directory - this includes output of Windows Event Log which is key to investigating issues with Virgo)


SAFR Web Console

SubjectWeb Cosole Events page does not show any events.  Only shows loading animation after 5 minutes.  Chrome reports page unresponsive.

Product

SAFR Web Console / 3.3 / Chrome

Steps to repro

Open Web Console
Go to Events page
Set time range to 24 hours
Wait for events
Observe chrome reports page unresponsive after 50 seconds. Click Wait.
After 5 minutes observe no events are shown

Expected result

Events appear within 10 seconds

Actual result

No events after 5 minutes

Description

We installed SAFR Desktop and found that events do appear in SAFR Desktop.  In that application we see 44356 events are shown.
<screenshot of web console events page>

Server has 25 cameras with high traffic in all cameras.
Attachments


REST APIs

SubjectGET /events API is returning MethodArgumentNotValidException

Product

SAFR REST APIs / 3.x / Events Service (CVEV)

Steps to repro

Run following API command:
Posting event with https://cv-event.real.com/event

HEADERS: {'Content-Type': 'application/json;charset=UTF-8', 'accept': 'application/json;charset=UTF-8'}
{'X-RPC-AUTHORIZATION': '***', 'X-RPC-DIRECTORY': 'main'}

BODY:
{"eventId":"90791680-9F16-4CF0-81DE-7D167EC78B44","siteId":"Site1","sourceId":"FaceTime", "date":1643239257956,"startTime":1643239257661, "endTime":1643239267862,"type":"person", "rootPersonId":"038340b2-6f7d-47ac-86cb-098398ab4ff0", "rootPersonAddDate":1599535404000.0}

Observe following response:

{"message":"MethodArgumentNotValidException", "errorReason":"ClientError",
"error":"MethodArgumentNotValidException", "path":"/event",
"verb":"POST", "status":400, "timestamp":1643245343198}



Expected 

result

Success or clear error indicating what argument is not valid.

Actual result

Above error message

Description

I am trying to update an existing event using above request.  I cannot tell what is wrong with the request.  Please advise.
Attachments<Log file of rqeuest/response details>  (Make sure to remove passwords and any other sensitive data)




SDK

SubjectSAFR Android Embedded SDK is crashing when passing face image

Product

SAFR SDK / 3.8 / Android ARM

Steps to repro

Provide clear code samples and any sample data needed to reproduce the issue such as a face image that generates undesirable result.

List steps needed to cause the issue to occur

Provide the full output from SDK (remove any sensitive data)

Expected result

Image is accepted without error and recognition is performed.

Actual result

Image is rejected, and SDK crash as provided above occurs.

Description

We are trying to recognize a face image with attached image. Image is obtained from ...
Attachments<face image>  (data will not be made public but do not include private user data)