Creating and running custom console traces for Security Center - Security Center 5.7 - 5.12

Working with logs and traces for Security Center

Applies to
Security Center 5.7 - 5.12
Last updated
2023-08-25
Content type
Troubleshooting
Language
English
ContentOps
ContentSoltution
Product
Security Center
Version
5.12
5.11
5.10
5.9
5.8
5.7

You can use custom console traces to regroup and run different loggers that are not combined in the default Server Admin list.

Procedure

  1. In your browser, open and log in to Server Admin.
    You can access the consoles for Security Center client applications at the following addresses:
    • Server Admin: localhost/Genetec/Overview
    • Security Desk: localhost:6020/Genetec/Overview
    • Config Tool: localhost:6021/Genetec/Overview
    • Genetecâ„¢ Mobile: localhost:9001/Genetec/console#/Diagnostic
  2. From the Servers list, select your server, and click Actions > Console.
    Server page in Server Admin with the list of actions displayed.
  3. Click the Trace logger tab.
    Trace logger page in Server Admin.
  4. Click Add () and configure the new trace:
    1. Enter a Name.
    2. (Optional) Configure the Retention policy and Disk usage and log file size settings.
    3. (Optional) In the Log folder field, change the default file location.
      Some logs can take up considerable space. To avoid issues with your system's performance or hard drive storage, it is recommended to save your log files somewhere other than your C: drive or anywhere recordings are stored.

      The default location for logs is C:\ProgramData\Genetec Security Center [X.Y]\Logs, where [X.Y] is the version of Security Center installed on your system.

      NOTE: The ProgramData folder can be hidden by default. If you do not see the ProgramData folder, consult the Microsoft Support website: https://support.microsoft.com on how to show hidden folders for the Windows version that you are using.
    4. Click and search the logger names.
      The logger names are provided by Technical Support.
    5. Select the loggers.
  5. Click Save.
  6. Select your new custom trace from the list and click Start ().
    The console trace starts running.
  7. While the trace is running, reproduce your issue and note the exact time when it occurs.
  8. After the issue is logged, click Stop () to stop the trace.
    IMPORTANT: Unless you stop the trace, it continues to run. If a trace continues running unchecked, it consumes more disk space than needed, making your server's hard drive unusable or causing system failures.
  9. Retrieve your log files and send them to Technical Support.
    Ensure you mention the time when the issue occurred during the trace.