[//]: # (title: IDE Infrastructure) ### Logging The IntelliJ platform uses [`Logger`](upsource:///platform/util/src/com/intellij/openapi/diagnostic/Logger.java) abstraction class to shield from underlying logging implementation and configuration. Plugins should obtain a dedicated instance: ```java import com.intellij.openapi.diagnostic.Logger; public class MyPluginFunctionality { private static final Logger LOG = Logger.getInstance(MyPluginFunctionality.class); public void someMethod() { LOG.info("someMethod() was called"); } } ``` ```kotlin private val LOG = logger() class MyPluginFunctionality { fun someMethod() { LOG.info("someMethod() was called") } } ``` If logging is used only to report exceptions, use convenience method `thisLogger()`: ```kotlin try { // some code } catch (e: Throwable) { thisLogger().error("some code failed", e) } ``` By default, all messages with level `INFO` and higher are written to log output file idea.log. To enable `DEBUG`/`TRACE` logging for specific categories, use Help | Diagnostic Tools | Debug Log Settings. To locate the log file, choose the Help | Show Log in Finder/Explorer action. When [internal mode](enabling_internal.md) is enabled, the currently running IDE log file can be opened using Help | Open Log in Editor. To locate it for a specific installation, see this [Knowledge Base article](https://intellij-support.jetbrains.com/hc/en-us/articles/206544519). See [Development Instance Sandbox Directory](ide_development_instance.md#the-development-instance-sandbox-directory) on how to find it for development instances. See [Testing FAQ](testing_faq.md) on how to enable `DEBUG`/`TRACE` level logging during tests, and obtain separate logs for failing tests. To provide additional context for [reporting fatal errors](#error-reporting), use `Logger.error()` methods taking additional `Attachment` (see [`AttachmentFactory`](upsource:///platform/core-impl/src/com/intellij/diagnostic/AttachmentFactory.java)). ## Error Reporting The IDE will show fatal errors caught by itself as well as logging messages with `ERROR` level in the IDE Fatal Errors dialog: - for IDE platform: in EAP releases or when running in [internal mode](enabling_internal.md) - for third-party plugins: always For the latter, 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`](upsource:///platform/platform-api/src/com/intellij/openapi/diagnostic/ErrorReportSubmitter.java) registered in extension point `com.intellij.errorHandler`. See [IntelliJ Platform Explorer](https://jb.gg/ipe?extensions=com.intellij.errorHandler) for existing implementations - ranging from pre-filling web-based issue tracker forms to fully automated submission to log monitoring systems. This [tutorial](https://www.plugin-dev.com/intellij/general/error-reporting/) also offers a working solution for using _Sentry_. ## Runtime Information [`ApplicationInfo`](upsource:///platform/core-api/src/com/intellij/openapi/application/ApplicationInfo.java) provides information on the IDE version and vendor. NOTE: to restrict compatibility, declare [IDEs](plugin_compatibility.md) and [versions](build_number_ranges.md) via plugin.xml. To obtain information about OS and Java VM, use [`SystemInfo`](upsource:///platform/util/src/com/intellij/openapi/util/SystemInfo.java). To access relevant configuration directories, see [`PathManager`](upsource:///platform/util/src/com/intellij/openapi/application/PathManager.java). ## Context Help To show custom context web-based help for your plugin's functionality (e.g., for [dialogs](dialog_wrapper.md)), provide [`WebHelpProvider`](upsource:///platform/platform-api/src/com/intellij/openapi/help/WebHelpProvider.java) registered in `com.intellij.webHelpProvider` extension point. ## Running Tasks Once Use [`RunOnceUtil`](upsource:///platform/core-api/src/com/intellij/ide/util/RunOnceUtil.java) to run a task exactly once per project/application.