This option controls the level of detail which is written to the SureSync job log when a synchronization is run. 4 different levels of detail can be selected. This setting becomes the default for all Relations, Schedules and Real-Time Monitors. The default logging level is level 6.
You can also configure a custom logging level for individual Schedules and Real-Time Monitors. For example, you might select a lower logging level such as '5 - Job Summaries and All Errors' as the default and set level '6 - All Details and Errors' just for critical jobs needing that level of detail. This eliminates some database overhead and keeps the size of the database smaller. Logging options can be set for an individual Schedule or Real-Time Monitor by clicking on the 'Logging' tab for the item in question.
Logging Level
Description
4 - All Exceptions, Warnings and Errors
Will record all errors and informational items.
5 - Job Summary and All Errors
Will record all errors and informational items and summary lines (duration, # of adds, # of deletes, etc.) for every Relation and Schedule run.
6 - All Details and Errors
Will record all events and errors that occur when a synchronization job is run, including entries for every copy, removal, etc. that is performed, as well as summary lines.
7 - Trace, Details and Errors
Will record all events and errors that occur when a synchronization job is run, including entries for every copy, removal, etc. that is performed, as well as summary lines and tech support trace lines. (Tech Support use)
Windows Event Log recording level
The 'Windows Event Log recording level' option allows you to configure the level of detail which should be written to the Windows Event Log when a synchronization is run. There are 6 different levels of detail. This setting becomes the default for all Relations, Schedules and Real-Time Monitors. You can also specify custom settings for each individual SureSync job by going to the 'Logging' tab of that particular job.
The levels of Windows Even Log reporting are defined in the table below.
Logging Level
Description
0 - No logging to Event Log
No logging will be entered into the Event Log.
1 - Application Failure Only
Will only record application errors. No synchronization errors will be recorded unless the application goes down.
2 - Job Failures and Severe Errors
Will only record application errors, or errors that cause a synchronization to fail or stop prematurely.
3 - Warnings, Job Failures, and Severe Errors
Will record all errors.
4 - All Exceptions, Warnings and Errors
Will record all errors and informational items.
5 - Job Summaries and All Errors
Will record all errors and informational items and summary lines (duration, # of adds, # of deletes, etc.) for every Relation and Schedule run.
Purge log entries older than
This option defines the number of days to retain old job log entries. SureSync will automatically purge entries older than the number of days defined here. If the checkbox is not checked, SureSync will not automatically delete any records out of the job log.
Job log entries are stored in the SureSync database. If you are storing detailed logging (level 6 or 7) in the database for a long span of time, you will experience some level of database bloat. We recommend purging old logs from the database. 14 days is the default for this setting. Logs can be exported to Excel spreadsheets for long-term storage if needed.
Trace
The trace section of this panel contains a number of diagnostic logs which can be generated for troubleshooting purposes. These options should only be enabled when requested by the Technical Support Team.
Traces should only be enabled when instructed by the technical support staff. Tracing adds overhead to the synchronization process and also consumes hard drive space to write the logs.
Trace Type
Description
Trace User Interface
This option will trace diagnostic troubleshooting information for the graphical user interface components of SureSync.
Trace Scheduler
This option will trace diagnostic troubleshooting information for the SureSync Scheduler service.
Trace All Jobs
This option will trace diagnostic troubleshooting information for any Relation, Schedule, or Real-Time Monitor which is run after the option is enabled. Job tracing can also be enabled on an individual Schedule or Real-Time Monitor to limit the amount of trace data generated.
Use Wrap Traces
This option is enabled along with one of the other three traces. Turns on a special type of trace which is generated only when an error occurs. Useful for catching very sporadic problems.
Job Trace Folder
This field allows you to define a custom folder to generate Job traces in. This can make the traces easier to find.
User Interface Trace Folder
This field allows you to define a custom folder to generate User Interface traces in.
Trace files can get big when dealing with large synchronization jobs. This can lead to problems having adequate free space available on machines with small amounts of hard drive space on the drive SureSync is installed on. The default location for all traces is C:\Documents and Settings\All Users\Application Data\Software Pursuits\SureSync (for the full SureSync installation) and C:\Documents and Settings\All Users\Application Data\Software Pursuits\SPIAgentService (for the SPIAgent only installation). If your C: has limited space you can enter in an alternate local path in the 'Trace Output Folder' field. For example you might use D:\Traces.
Traces should only be enabled when instructed by the technical support staff. Tracing adds overhead to the synchronization process and also consumes hard drive space to write the logs.
You can also configure a custom logging level for individual Schedules and Real-Time Monitors. For example, you might select a lower logging level such as '5 - Job Summaries and All Errors' as the default and set level '6 - All Details and Errors' just for critical jobs needing that level of detail. This eliminates some database overhead and keeps the size of the database smaller. Logging options can be set for an individual Schedule or Real-Time Monitor by clicking on the 'Logging' tab for the item in question.