Logging

GlueSync by default logs its status in the system’s output console. This process can be customized tweaking the logging configuration file according to the logback’s framework documentation available at: http://logback.qos.ch/documentation.html. This let the user have a great control under the hood and a wider flexibility to decide which logs you want to collect (also for GDPR purposes) and where they should be stored.

To provide GlueSync a custom Logback configuration file, you need to set the actual file path into an environment variable called LOG_CONFIG_FILE. Once set, GlueSync will override its default log settings and use the provided ones.

LOG_CONFIG_FILE=/path/to/logback.xml

Below you can find the default configuration file used by our professional services.

<?xml version="1.0" encoding="UTF-8"?>
<included>
   <appender name="CONSOLE" class="ch.qos.logback.core.ConsoleAppender">
       <encoder>
           <pattern>
               %d{yyyy-MM-dd'T'HH:mm:ss.SSS} [%t] %c{0} %p - %msg%n
           </pattern>
       </encoder>
   </appender>
   <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
       <file>/var/log/gluesync/gluesync.log</file>
       <rollingPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy">
           <fileNamePattern>/var/log/gluesync/archived/gluesync.%d{yyyy-MM-dd}.%i.log</fileNamePattern>
           <!-- each archived file, size max 10MB -->
           <maxFileSize>10MB</maxFileSize>
           <!-- total size of all archive files, if total size > 20GB, it will delete old archived file -->
           <totalSizeCap>20GB</totalSizeCap>
           <!-- 60 days to keep -->
           <maxHistory>60</maxHistory>
       </rollingPolicy>
       <encoder>
           <pattern>%d{yyyy-MM-dd'T'HH:mm:ss.SSS} %c{1} %p %m%n</pattern>
       </encoder>
   </appender>
   <logger name="com.gluesync" level="debug" additivity="false">
       <appender-ref ref="CONSOLE"/>
       <appender-ref ref="FILE"/>
   </logger>
</included>