Hey Martin,
you can modify the FirstSpirit logging by means of Log4J (configuration files are also located at <server_root>/conf(fs-logging.*.conf) at your own risk (please consult the official Log4J documentation at https://logging.apache.org/log4j/1.2/manual.html😞
If the onboard possibilies are not suffient then you can provide own appenders by adding jar files to <server_root>/shared/lib.
I have not test this but on github you can find this:
https://github.com/damiendallimore/SplunkJavaLogging
Or without a foreign library by means of log4j you can to this according to the splunk people:
https://answers.splunk.com/answers/5133/log4j-socket-appender-and-splunk.html#answer-5158
The (network) socket appender mentioned above can be tested with Log4Js chainsaw tool:
https://logging.apache.org/chainsaw/
I did that in the past with a lot of Java projects myself when I want to filter log events in real time (instead of opening a log file).
Personally I like the idea to add an own Log4J appender definition and add it to the root category. So you would leave the FirstSpirit logging facility (fs-appender) untouched. Then you specify what kind of format the appender might have and where it puts the data (may it a file, network, database or email).
Regards
Marian
