Configure Connectivity Hub Log Files

Administration Site Logs

BA Insight provides a predefined configuration file for the administration site, Logging.config, which you can edit in Notepad to specify operations such as:

  • Specify parameters, like log level, buffer size and log file location

This operations are automatically applied when the logs are written.

To see or edit the Logging.config for the admin site, navigate to the Connectivity_Hub_root  -> Admin Site - >Logging.config

To see the log entries, navigate to the folder where ConnectivityHub is installed > Admin Site > Logs

In general, you should view the log files located here to discover why:

  • You cannot save a specific content or connection
  • You cannot an exception when performing an UI operation, like opening a target, dataset etc
  • You cannot connect to cache/configuration database
  • Content test bench shows an exception/error/warning 

Timer Job Logs

BA Insight provides a predefined configuration file for the scheduler service, Logging.config, which you can edit in Notepad to specify operations such as:

  • Specify parameters, like log level, buffer size and log file location
  1. These operations are automatically applied when the logs are written.
  2. To see or edit the Logging.config for scheduler service, navigate to the folder where ConnectivityHub is installed > Quartz Server >Logging.config.
  3. To see the log entries, navigate to the folder where ConnectivityHub is installed  > Quartz Server > Logs.



  4. Depending on the logging level selected while starting or scheduling a job, all or a part of the log entries can be seen from Admin Site > Tools > Logs

    See the Logs page.

  5. The information logged by each task in particular can also be seen from Tasks > Actions > View Logs



  6. You should check the Timer Job Logs for:
  • Unexpected behavior when you run the target sync.
  • Items missing from incremental crawl.
  • Unexpected behavior when you run Security Sync or any other connection task.

Tune Your Log Configuration Settings

Change the following attributes of log file to suit your logging requirements.

Tip: Do not change the value "ALL" of the <level> element found inside the <root> section of the Logging.config file.

  • To change the level for the file logging, set the value of the <threshold> element found in the "DefaultRollingFileAppender" appender section.
  • To modify the level of the logs that can be seen in the UI, set the "Log level" value from the drop-down box while starting or scheduling a new job.

Note: Changing thelog level from the default (INFO) to another level such asDEBUGorTRACE, generates more log entries in the log file.

  • (This comparison is based on the default log level and impacts crawl performance.)
  • For this reason, only change a log level setting if additional information is required for troubleshooting.
  • For the best performance, set your normal production logging level toINFO.


Parameter Description
threshold value

Define the log severity level. All items are case-sensitive:

  • FATAL:
    • Records critical errors that make the system unusable.
  • ERROR: 
    • Records execution failures in the program.
  • WARN: 
    • Records potential failures that are not critical to the execution of the program.
    • This log level logs only warnings and errors in order to catch obvious problems.

    • INFO:

    • Default

    • Records the completion of different stages of the logged process, and other information as notes. 
    • These logs also display everything thatWARNdoes in addition toINFO messages and lets support, solutions, and developers resolve less obvious issues such as items:
      • that were missed after a crawl
      • that were not removed from the index

      • whose security is not updated

      • Note: Log File size: The maximum space that is used by the WARN and INFOlog files is 500 MB

  • Debug:
    • Use for deeper troubleshooting. Shows technical details required to resolve most errors and issues. These logs display everything thatINFOlog files show as well as some debugging information. The maximum space that is used by these log files is 4GB.
  • TRACE:
    • Records full details for troubleshooting, and contains all of the log messages. 
    • The temporary files that are created at runtime for processed items, are not deleted.
    • Additional report files are created during any incremental crawls.
    • For this reason, the TRACE files are the most verbose of the log files. 
    • The maximum space that is used by these log files is 16GB.)
      These details include:
      • All of the log messages
      • Temp files that are created for processed items
      • Additional report files that are created during incremental crawls. (These files haveEnumReportorItemReportin their names and the.dataextension.) These files contain items that are enumerated by the crawl.
maximumFileSize

  • Default: 10MB

  • Set the maximum log file size to archive, in bytes (also supports suffixes like KB and MB). 
maxSizeRollBackups

  • Default: 10

  • Set the maximum number of log files to archive.

Note: For more information and a detailed description of the logging configuration file, seeApache Log4net.