Configuration Descriptor: Logger Configuration

# This configuration provides the information to the CT framework for handling its logging
##############################################################################

# This flag is used to turn on of off logging by CT Framework. 
# Turning this off would mean that even Exceptions faced will not be logged to any log file!!!
LOGGING_ENABLED_IND=true

# Indicate the log4j2 adaptor class that we want Canvas to use.
#LOGGER_CLASS = com.intellectdesign.canvas.logging.log4j2.CanvasLog4j2LoggerImpl

# Indicate the exact adaptor class that we want Canvas to use.
LOGGER_CLASS = com.intellectdesign.canvas.logging.log4j1x.CanvasSLF4jLoggerImpl

# Indicate the log4j override file for this application
CT_LOG4J_OVERRIDE_FILE=Sigma-log4j.xml

# Indicate the log4j configuration file to override the default one provided by framework. Configure this value to override xml and ensure the default
# appenders from work also present in the override file.
# In case of log4j2 is used, the framework also supports to write the logs in the JSON format instead of log file pattern. To enable this use the following 
# file from CTLogging-Log4j-2x.jar as below. If you need any customization to this configuration please copy the contents of the file to your customized file
# and configure the same for below property.
# For sigma we have customized json configuration file. You can use this configuration for json logging.
#CT_LOG4J_OVERRIDE_FILE=Sigma-json-log4j2.xml

# This configuration holds the path where the log files are to be created.
# This path configured should be relative to the root path that is configured as CT_WORK_FOLDER_PATH in implementation property file.
log.path=/logs

# The below configuration is for controlling the logging level.
# Possible values are - debug, error, info, fatal, warn, off. Default if not provided # is "debug".
log.level = info

# The log.level is set as the default log level for all modules within Canvas.
# In case you want to override at individual module level, then you can use the 
# below options to override the same.
# Module name Canvas Module
# ------------ -----------------------------------
# audit Audit handling module
# alert handling module
# session management layers
# web layer modules
# config Configuration module
# cache framework
# security module
# database module
# entitlement module
# event definition & handling module
# export framework
# vdf Meta data frameworks
# hal Host Access Layer
# report Reporting module
# validator Validation module
# scheduler module 
log.level.audit = debug
log.level.alert = error
log.level.session = info
log.level.web = debug
log.level.config = info
log.level.cache = debug
log.level.security = info
log.level.database = debug
log.level.entitlement = info
log.level.event = debug
log.level.export = debug
log.level.vdf = debug
log.level.hal = debug
log.level.report = debug
log.level.validator = debug
log.level.scheduler = debug
log.level.reqmodel = debug
log.level.dataimport = debug

# Canvas uses Log4J as the internal logging library and uses a RollingFileAppender for handling logging. 
# The following set of configuration apply for how the logging is handled.

# It should be noted the below configuration are optional. The default values if not provided is also 
# indicated against each configuration. 

# The following attribute 'rolloverModel' allows to choose any of the 2 models supported by Canvas Log appender namely:

# A. CREATENEW - Current logging would happen in the file name having the current date pattern 
# and the highest rolling index value. (i.e., logging would happen by creating a new file)

# B. BACKUPOLD - Current logging would always happen in file name without date pattern and 
# rolling index, on roll over the current file would be made as a backup with a date pattern and 
# index included in it.

# The default used is BACKUPOLD 
rollovermodel = BACKUPOLD

# The following attribute 'datepattern' decides on the following 2 aspects:

# A. the period when the rollover should happen (i.e.) daily, monthly, yearly etc.
# For example:
# yyyy-MM >> Roll over at the beginning of each month
# yyyy-ww >> Roll over at the first day of each week. The first day of the week depends on the locale.
# yyyy-MM-dd >> Roll over at midnight each day.
# yyyy-MM-dd-a >> Roll over at midnight and midday of each day.
# yyyy-MM-dd-HH >> Roll over at the top of every hour.
# yyyy-MM-dd-HH-mm >> Roll over at the beginning of every minute.

# B. The Date format to be displayed in the log file name generated.
# For Example:
# ddMMMyyyy - generates log file name with date stamp in the file name as 20MAR2010

# yyyy-MM-dd - generates log file name with date stamp in the file name as 2010-03-20
# The default used is yyyy-MM-dd.
datepattern = yyyy-MM-dd

# The following attribute 'maxsizelimit' decides on the maximum file size of a log file 
# considering the rollover period.
# For a period if the file size exceeds the set value a new file with same period would 
# be generated with rolling index incremented by one.
# The appender expects size value in "KB", "MB" or "GB"
# The default value is 10MB.
maxsizelimit = 10MB

# The appender expects the following two options:
# 1. SUFFIX
# 2. PREFIX
# based on which the appender will create the log file name in the following format or pattern:

# a. <filename><patternSeparator><datePattern><patternSeparator><rollingIndex>.<extension> if the suffixOrPrefix option is 'PREFIX'
# Example: serverLogs-2010-03-26-01.log

# b. <filename>.<extension><patternSeparator><datePattern><patternSeparator><rollingIndex> if the suffixOrPrefix option is 'SUFFIX'
# Example: serverLogs.log-2010-03-26-01

# The default value is PREFIX.
suffixorprefix = PREFIX

# The appender expects any character except ':' that actually separates the date
# pattern in the file name with other components of the file name.
# The default value is -
patternseparator = -