Logger initialized with foreign class

Reports Logger instances initialized with a class literal other than the class the Logger resides in.

This can happen when copy-pasting from another class. It may result in logging events under an unexpected category and incorrect filtering.

Use the inspection options to specify the logger factory classes and methods recognized by this inspection.

Example:

class AnotherService
class MyService {
    private val logger = LoggerFactory.getLogger(AnotherService::class.java)
}

After the quick-fix is applied:

class MyService {
    private val logger = LoggerFactory.getLogger(MyService::class.java)
}

Locating this inspection

By ID

Can be used to locate inspection in e.g. Qodana configuration files, where you can quickly enable or disable it, or adjust its settings.

KotlinLoggerInitializedWithForeignClass

Via Settings dialog

Path to the inspection settings via IntelliJ Platform IDE Settings dialog, when you need to adjust inspection settings directly from your IDE.

Settings or Preferences | Editor | Inspections | Kotlin | Logging

Inspection options

Here you can find the description of settings available for the Logger initialized with foreign class inspection, and the reference of their default values.

Suppressing Inspection

You can suppress this inspection by placing the following comment marker before the code fragment where you no longer want messages from this inspection to appear:

//noinspection KotlinLoggerInitializedWithForeignClass

More detailed instructions as well as other ways and options that you have can be found in the product documentation:

IntelliJ IDEA 2025.2

Inspection Details
By default bundled with:	IntelliJ IDEA 2025.2, Qodana for JVM 2025.2,

Last modified: 18 September 2025