[
http://jira.qos.ch/browse/LBCLASSIC-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ceki Gulcu resolved LBCLASSIC-187.
----------------------------------
Fix Version/s: 0.9.19
Resolution: Fixed
Solved in http://github.com/ceki/logback/commit/1fd3f4ed5e26bd3ddff5
> Log request arguments should be placed in separate columns
> ----------------------------------------------------------
>
> Key: LBCLASSIC-187
> URL: http://jira.qos.ch/browse/LBCLASSIC-187
> Project: logback-classic
> Issue Type: Sub-task
> Components: appender
> Affects Versions: 0.9.18
> Reporter: Ceki Gulcu
> Assignee: Logback dev list
> Fix For: 0.9.19
>
>
> Originally reported by Greg Thomas:
> http://jira.qos.ch/browse/LBCLASSIC-169?focusedCommentId=11565#action_11565
> I'm not so much interested in table/column names, but what I would like to
> see is the ability to record the individual values for the placeholders in
> the log message.
> If you're logging to a database, there's the possibility of running report on
> that database. Instead of having to parse out the data from the re-combined
> log message (e.g. "New call made; now 4 calls active"), it would be easier to
> record the value of arguments directly in the database. e.g. if you've
> configured it so that the first argument is stored in column arg1, and the
> second is stored in arg2, then the log entry
> logger.info( "New call made; now {} calls active", activeCallCount );
> could appear in the database as (ignoring the other columns for this example)
> ...
> formatted_message: "New call made; now 4 calls active"
> arg1: "4"
> arg2: null
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.qos.ch/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
[email protected]
http://qos.ch/mailman/listinfo/logback-dev
