On Friday, 18 October 2013 at 16:01:30 UTC, Dicebot wrote:
On Friday, 18 October 2013 at 15:29:09 UTC, ilya-stromberg
wrote:
About syntax - we can use something like this:
log!(user, server, errorCode)(LOGIN_FAILED_UUID, "Couldn't log
in");
That will be template instance bloat disaster for so
On Friday, 18 October 2013 at 15:29:09 UTC, ilya-stromberg wrote:
About syntax - we can use something like this:
log!(user, server, errorCode)(LOGIN_FAILED_UUID, "Couldn't log
in");
That will be template instance bloat disaster for something used
as commonly as log function (comparing to a ty
On Tuesday, 15 October 2013 at 15:21:52 UTC, Johannes Pfau wrote:
I think one increasingly important point for std.log is
'structured
logging'.
Structured logging is basically not simply logging textual
messages, but
also logging additional KEY/VALUE pairs of data. The idea is
that logs
shou
On Tuesday, 15 October 2013 at 15:53:34 UTC, Robert Schadek wrote:
That been said, you can add it. The method Logger.logf is a
variadic
template. You can simple create your own Logger Class and
overwrite that
method and implemented your structured logging approach there.
The only
pitfall is tha
On 10/15/2013 05:20 PM, Johannes Pfau wrote:
> I think one increasingly important point for std.log is 'structured
> logging'.
>
> Structured logging is basically not simply logging textual messages, but
> also logging additional KEY/VALUE pairs of data. The idea is that logs
> should not only be r
I think one increasingly important point for std.log is 'structured
logging'.
Structured logging is basically not simply logging textual messages, but
also logging additional KEY/VALUE pairs of data. The idea is that logs
should not only be readable by humans but also easy to parse and
analyze. St
