Log format
The expected format for this device, which is the default logging format, is:
Date Time Severity Class Thread LogID: Message
It is defined by the following string:
%d{yyyy-MM-dd HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%nLog sample
This is a sample log from a Red Hat WildFly 8 device:
2017-05-15 02:22:20,825 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "fiveseries.war"
The expected format for the server.log is:
2017-02-16 21:53:19,520 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management 2014-02-16 21:53:19,523 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990 2017-02-16 21:53:19,525 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.0.0.Final\"WildFly\" started in 38820ms - Started 305 of 361 services (93 services are lazy, passive or on-demand)
Field mapping
This table shows the mapping between the data source and Trellix ESM fields.
Log fields | Trellix ESM fields |
|---|---|
Date Time | First Time, Last Time |
LogID | Signature ID, External_EventID |
Class | Target_Class |
Severity | Severity |