Request clarification before answering.
It's the Tanuki wrapper that is adding the timestamp. I think it just captures all output from stdout and stderr and logs it but doesn't have the concept of multi line messages so each line gets its own timestamp.
I ended up configuring log4j to log to a separate file with a pattern that I could control and sent that to our log aggregation.
There are also some messages that come through java util logging and you can send these to a file by editing bin/platform/tomcat/bin/jdk_logging.properties
e.g. the message marked SEVERE: in your screenshot is a JUL message, the one marked ERROR is a log4j message
You miss messages that come directly from the wrapper, specifically server startup and shutdown but it's much easier to parse multi line messages.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you are using splunk then you can change the view settings to hide the log level server deails and so on... you can check the filters... in splunk
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.