The IntelliJ platform uses
Logger abstraction class to shield from underlying logging implementation and configuration.
Plugins should obtain a dedicated instance:
If logging is used only to report exceptions, use convenience method
By default, all messages with level
INFO and higher are written to log output file idea.log. To enable
TRACE logging for specific categories, use .
To locate the log file, choose the internal mode is enabled, the currently running IDE log file can be opened using .action. When
See Testing FAQ on how to enable
TRACE level logging during tests, and obtain separate logs for failing tests.
Fatal errors and logging messages with
ERROR level will be shown in the IDE Fatal Errors dialog for EAP releases or when running in internal mode. For errors caused by third-party plugins, reporting is disabled by default - instead, there's an option to disable the plugin causing the exception.
To let users report such errors to the vendor, plugins can implement custom
ErrorReportSubmitter registered in extension point
com.intellij.errorHandler. See IntelliJ Platform Explorer for existing implementations - ranging from pre-filling web-based issue tracker forms to fully automated submission to log monitoring systems.
To obtain information about OS and Java VM, use
To access relevant configuration directories, see