Create different instance or store to a different file

[AlexandruDev]

Create different instance or store to a different file

[MFlisar]

I just made an update and extracted some logic of the daily setup into a base class that can be reused by new setups.

Check out the current existing implemtations:

Lumberjack/library/loggers/lumberjack/file/src/main/java/com/michaelflisar/lumberjack/loggers/file/FileLoggerSetup.kt

Lines 57 to 61 in 49ee875

	override fun getFileKey(data: FileLogger.Event.Data, lastPath: String): String {
	date.time = data.time
	val key = timeFormatter.format(date)
	return key
	}

Lumberjack/library/loggers/lumberjack/file/src/main/java/com/michaelflisar/lumberjack/loggers/file/FileLoggerSetup.kt

Lines 109 to 124 in 49ee875

	override fun getFileKey(data: FileLogger.Event.Data, lastPath: String): String {
	if (fileIndex == null) {
	// we must find out what the highest existing log file index currently is
	fileIndex =
	getAllExistingLogFiles().lastOrNull()?.let { getKeyFromFile(it).toIntOrNull() }
	?: 1
	}
	if (lastPath.isEmpty()) {
	return fileIndex.toString()
	}
	val bytes = File(lastPath).takeIf { it.exists() }?.length()
	if ((bytes ?: 0L) >= maxFileSizeInBytes) {
	fileIndex = fileIndex!! + 1
	}
	return fileIndex.toString()
	}

Suggestion

I do pass in FileLogger.Event.Data to the getFileKey function now, this allows you to decide which file name is the correct one based on this data, it should contain everything you need to make your decision. The base setup will create log files based on the file key like following:

Lumberjack/library/loggers/lumberjack/file/src/main/java/com/michaelflisar/lumberjack/loggers/file/BaseFileLoggerSetup.kt

Line 25 in 49ee875

val path = "${folder.path}/${fileBaseName}_${key}.$fileExtension"

I would do following:

• create your own setup implementation
• derive a key from the class name
• be aware, that the logging implemention in the background will close/open log files whenever the key changes - everthing is done on a backgroud thread, still keep that in mind

I don't know why you really need files for each class, maybe think about using multiple instances of FileLoggers and add some filter to them 'FileLogger(setup, filter = ...)`?

[AlexandruDev]

Thank you @MFlisar, I managed to create a different log file for the activity responsible with the incoming/outgoing calls and a separate one for the entire app.

I'l close this.