<span class="pill kill-chain">_time</span>
<span class="pill kill-chain">host</span>
<span class="pill kill-chain">source</span>
<span class="pill kill-chain">sourcetype</span>
<span class="pill kill-chain">jvm_pid</span>
<span class="pill kill-chain">_raw</span>
</div>
Data Source: Java HotSpot Fatal Error
Description
HotSpot fatal error reports are created only after a fatal JVM error. Without -XX:ErrorFile, the JDK tries to write hs_err_pid
To make collection predictable, set a writable absolute path such as -XX:ErrorFile=/var/log/myapp/hs_err_pid%p.log in the JVM startup options. For Tomcat scripts use CATALINA_OPTS in setenv.sh or setenv.bat; for a Windows Tomcat service use its Java options. For Spring Boot set the Java service/container arguments. For Elasticsearch inspect its existing -XX:ErrorFile setting in jvm.options before changing it. Monitor the chosen path as java:hotspot:fatal. Extract jvm_pid from the hs_err_pid filename if needed; these reports do not share the unified-log [time][pid][level][tags] format or guarantee a jvm_message field. A fatal report is not a required result of exploitation.
JDK fatal-error location: https://docs.oracle.com/en/java/javase/24/troubleshoot/location-fatal-error-log.html Elasticsearch JVM settings: https://www.elastic.co/docs/reference/elasticsearch/jvm-settings
Details
| Property | Value |
|---|---|
| Source | hs_err_pid*.log |
| Sourcetype | java:hotspot:fatal |
Event Fields
Example Log
1A fatal error has been detected by the Java Runtime Environment: SIGSEGV
Required Output Fields
-
jvm_pid
-
source
-
_raw
Source: GitHub | Version: 1