-
Notifications
You must be signed in to change notification settings - Fork 39
Getting a new line in the sql timing output which kills output cmd line handling with sed/awk #34
Comments
Can you describe what are you trying to do? |
I'm monitoring the logging output. We pump everything into one log file and then use the command line a bit like this: tail -f /app/gis/tst/tardis/catalina.out | cut -d ' ' -f 5 | awk '/sqltiming/ {printf("%.4d %s", $1, $4")}' Basically filtering and formatting the logging output. This doesn't work with the current version since the duration stats come out on the line below all the other columns in the logging output. Until I get the chance to clone your repo and produce a local upgrade release, I'm forced to use a different JDBC spy package that is probably a performance downgrade. |
@ADAM66 I think i may have experienced the same issue as you. I just added a new spy log delegator that removed any sql processing (which adds the new line). See private String buildSqlTimingDump(long execTime, String sql)
|
In class Slf4jSpyLogDelegator line 313 it looks like there is a bad new line inserted.
This is coming out in the sql timings logging and destroys the command line processing that I do to manipulate and filter the logging output, because the crucial information (duration) appears on the next line.
The text was updated successfully, but these errors were encountered: