Inconsistent Log Verbosity Across OS When Capturing Native Crash Dumps in JetBrains IDEs

Goal

When a deployment fails, the JetBrains IDE should provide a consistent, detailed log that captures native crash dumps regardless of the operating system. This consistency is essential for reproducing the issue and diagnosing the root cause across Windows, macOS, and Linux.

Constraints & Uncertainty

The IDE’s logging framework exposes per‑package log levels, but the verbosity of native crash dumps appears to vary by OS. The mechanism that triggers these dumps and the default log level applied to them is not clearly documented, leading to gaps when comparing logs from different environments.

Unresolved Questions

• Which internal log configuration controls the verbosity of native crash dumps across all supported operating systems?
• Is there a global setting or environment variable that can enforce a uniform log level for these dumps, ensuring identical output on Windows, macOS, and Linux?
• How does the JetBrains logging subsystem differentiate between Java‑level logs and native crash dump logs, and can this distinction be overridden?