Best practices for storing console traces - 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

Some logs can consume considerable disk space. To prevent issues with system performance and hard drive storage, there are a few best practices you should consider.

  • Save your log files somewhere other than the C: drive or anywhere recordings are stored.
    NOTE: 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.
  • After the issue is logged, stop the trace. Otherwise, it will continue to run and consume disk space.
  • Align your trace logging strategies with the available storage space. For each trace, configure the Retention policy and Disk usage and log file size settings:
    Delete files after
    Number of days the log files are retained. When the threshold is reached, the system deletes the files.
    Create file after
    Maximum number of lines for a single log file. When the threshold is reached, the system creates a new log file.
    Minimum available disk space
    Minimum disk space required for logging in MB or GB. When available disk space falls below the threshold, the logging stops and the system sends a notification. The logging resumes when disk space becomes available.
    Maximum disk space usage
    Maximum usable disk space for logging in MB or GB. When the threshold is reached, the system deletes old log files.
    Maximum log file size
    Maximum size for a single log file in MB or GB. When the threshold is reached, the system creates a new log file.
    Enable compression
    You can enable this option to compress the log file in ZIP format.