IDE Infrastructure

note

If your plugin uses the log4j library directly: it is removed from IntelliJ Platform in 2022.1; please see this blog post for migration instructions.

The IntelliJ Platform uses Logger abstraction class to shield from underlying logging implementation and configuration.

Plugins should get a dedicated instance:

import com.intellij.openapi.diagnostic.Logger;

public class MyClass {
  private static final Logger LOG = Logger.getInstance(MyClass.class);

  public void someMethod() {
    LOG.info("someMethod() was called");
  }
}

import com.intellij.openapi.diagnostic.logger

private val LOG = logger<MyClass>()

class MyClass {
  fun someMethod() {
    LOG.info("someMethod() was called")
  }
}

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 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. See Development Instance Sandbox Directory on how to find it for development instances.

See Testing FAQ on how to enable DEBUG/TRACE level logging during tests and get separate logs for failing tests.

To provide additional context for reporting fatal errors, use Logger.error() methods taking additional Attachment (see CoreAttachmentFactory and AttachmentFactory).

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

• 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 use one of the solutions:

• Use JetBrains Exception Analyzer (EA) that sends errors to the backend provided by JetBrains (2023.3+).

• Implement custom ErrorReportSubmitter registered in com.intellij.errorHandler extension point. See IntelliJ Platform Explorer for existing implementations — ranging from pre-filling web-based issue tracker forms to fully automated submission to log monitoring systems. This tutorial also offers a working solution for using Sentry.

The red exclamation notification icon in the status bar is controlled with the idea.fatal.error.notification system property. The property can be edited in idea.properties file opened with Help | Edit Custom Properties...:

• idea.fatal.error.notification=disabled hides the component

• any other value or the lack of the property enables the component

ApplicationInfo provides information on the IDE version and vendor. NOTE: to restrict compatibility, declare IDEs and versions via plugin.xml.

To get information about OS and Java VM, use SystemInfo.

To access relevant configuration directories, see PathManager.

To obtain unique installation UUID, use PermanentInstallationID. For paid plugins, see also Marketplace docs.

To show custom context web-based help for your plugin's functionality (e.g., for dialogs), provide WebHelpProvider registered in com.intellij.webHelpProvider extension point.

tip

To localize the help page URL, retrieve the current locale and language tag from the dynamic bundle.

Use RunOnceUtil to run a task exactly once per project/application.

Application lifecycle events can be tracked via the AppLifecycleListener listener. See also Application Startup and Project and Application Close.

Register the ApplicationActivationListener listener to be notified of "application focused/unfocused" events.

To request restart of the IDE, use Application.restart()

Use BrowserLauncher.

Use RevealFileAction.openFile() or openDirectory().

Use the LafManagerListener topic to receive change notifications (e.g., to refresh UI).

File | Power Save Mode can be enabled to limit power-consuming features on laptops. Use PowerSaveMode service and PowerSaveMode.Listener topic to disable such features in your plugin accordingly.

Installed plugins can be checked via PluginManagerCore.isPluginInstalled().

See also Plugin Load/Unload Events.

Use HttpConnectionUtils to use platform network settings (e.g., proxy) (2024.3). For earlier versions, see HttpConfigurable.