The operational parameters of the OSGi Log Bundle, exported by its Managed Service, can be conveniently configured through the Web Admin Console.


PID = mbs.log.FileLogAppender.Default
Factory PID = com.prosyst.mbs.impl.services.log.FileLogAppender
BundleLocation = ../../../bundles/com.prosyst.mbs.osgi.log.bundle.jar
customFormatter =
enabled = false
entriesThreshold = 100
logsDir = logs
maxBackupCount = 4
maxFileSize = 32768
mdcEnabled = false
service.factoryPid = com.prosyst.mbs.impl.services.log.FileLogAppender
service.pid = mbs.log.FileLogAppender.Default
timeThreshold = 10000
PID = com.prosyst.mbs.impl.services.log.FrameworkLogAppender
BundleLocation = ../../../bundles/com.prosyst.mbs.osgi.log.bundle.jar
enabled = true
mdcEnabled = false
service.pid = com.prosyst.mbs.impl.services.log.FrameworkLogAppender
PID = com.prosyst.mbs.impl.services.log.LogStackConfig
BundleLocation = ../../../bundles/com.prosyst.mbs.osgi.log.bundle.jar
level = 3
lineNumbersEnabled = false
logListenerTimeout = 10000
service.pid = com.prosyst.mbs.impl.services.log.LogStackConfig
threadNamesEnabled = false
PID = com.prosyst.mbs.impl.services.log.service.LogReaderFactory
BundleLocation = ../../../bundles/com.prosyst.mbs.osgi.log.bundle.jar
maxEntryCount = 100
service.pid = com.prosyst.mbs.impl.services.log.service.LogReaderFactory
Configuration status export as zip could be disabled by antivirus programs. If you happen to receive an empty zip configuration statuses (48 bytes long) you could try stopping your antivirus program before exporting.

PID = com.prosyst.mbs.impl.services.log.LogStackConfig
BundleLocation = ../../../bundles/com.prosyst.mbs.osgi.log.bundle.jar
level = 3
lineNumbersEnabled = true
logListenerTimeout = 10000
service.pid = com.prosyst.mbs.impl.services.log.LogStackConfig
threadNamesEnabled = true