name} - %X{bundle.version} | %m%n log4j.appender.out.file=${karaf.log}/karaf.log log4j.appender.out.append=true log4j.appender.out.maxFileSize=1MB log4j.appender.out.maxBackupIndex=10 # Sift appender log4j log4j.appender.sift.appender.file=${karaf.log}/$\\{bundle.name\\}.log log4j.appender.sift.appender.append=true The default configuration only define the ROOT logger, with INFO log level, using the out file %X{bundle.version} | %m%n"/> append="true" filePattern="${karaf.log}/$${date:yyyy-MM}/fuse-%d{MM-dd- yyyy}-%i.log.gz">

config config:cancel config:delete config:edit config:list config:property-append config:property-delete config:property-list config:property-set config:update connect in configuration edit mode. You are now ready to use other config commands (like config:property-append, config:property-delete, config:property-set, ...). If you provide a configuration PID that doesn't the configuration commit and rollback mechanism. 64 CONFIGURATION config:property-append The config:property-append is similar to config:property-set command, but instead of completely replacing the

cluster:config-property-list command: You can set or append a value to a config property using the cluster:config-property-set or cluster:config-property-append command: You can delete a property in a config

cluster:config-property-list command: You can set or append a value to a config property using the cluster:config-property-set or cluster:config-property-append command: You can delete a property in a config

dispatcher topics. By default, the appenders are listening on decanter/collect/* topics. If you want to append processed events, you have to configure the appenders to listen on decanter/process/* topics. To