Your Browser is Out of Date

Nytro.ai uses technology that works best in other browsers.
For a full experience use one of the browsers below
Design Guide—Virtualized Computer Vision for Smart Transportation with Genetec
Introduction Architecture concepts and requirements Solution Architecture Validation Sizing the solution Backup and restore operations Monitoring the solution Troubleshooting recommendations
BriefCam
Genetec
Ipsotek
Summary and conclusions References

BriefCam

BriefCam

  • Every service that is installed on a server creates a separate folder for writing log files. If more than one instance of a module is installed, a separate log folder is created which will have an increasing number value appended to its name. No folders or files are created for any module that is not installed. Log files are started fresh each day and organized by including their creation date in the filename when the daily log is closed. Log files do not store any sensitive data, such as passwords or access tokens. Administrators can also set a maximum log file size in case daily logs are getting too large to manage efficiently. There is also a setting to control when to trigger an automatic .zip archive creation based on the number of files created in a day.

    Information useful for troubleshooting BriefCam's Web Services can also be found in the Windows Internet Information Services (IIS) logs. The location of these logs for a default installation can be found in the following path and folders.

    Figure 14. Windows IIS log location example

    In addition to the BriefCam RESEARCH Service log files that are normally located at: C:\Program Files\BriefCam\BriefCam Server\logs\BIRuleEngineService-O , there are log files that are produced by the integration with the Qlik service. Qlik's trace log folder has separate log files for each element such as Engine and App Migration. See the BriefCam Administrators Guide for more detailed descriptions of troubleshooting tips using log files.