Early review of std.logger

Jeremy Powers jpowers at wyrdtech.com
Mon Oct 14 10:18:55 PDT 2013


Also:

* Asynchronous logging.  Log something and continue, not blocking on actual
message getting written.  Can write a custom logger that works this way,
but would be nice if this was supported at the base level.


On Mon, Oct 14, 2013 at 10:01 AM, Jeremy Powers <jpowers at wyrdtech.com>wrote:

> Some comments from the peanut gallery:
>
> * Mentioned already: configurable log output.  Configure style/contents of
> log output based on output location.  More options for included info
> (thread id, etc).  Allow custom info to be inserted based on logger context.
>
> * Also mentioned: Configurable log rotation for file logger.
>
> * Pass an exception to logger directly, have it output in message
> depending on configuration.  Pretty vs. short vs. all-one-line for
> automated log parsing.
>
> * Support multiple output locations.  Code calls log.whatever(), be able
> to have that spit out to various places (stdout, syslog, file, etc)
> depending on configuration. Be able to configure different logging levels
> for each output.
>
> * Should be able to change log levels via configuration, for debugging of
> existing code (during dev or production).  That is, be able to change each
> logger level without recompiling.
>
> * The 'critical' level seem extraneous - when would you use this instead
> of error or fatal?
>
> * Easy way to create logger per module, inheriting settings from logger
> hierarchy.  Associated way to manage loggers and their configuration.
>
>
> Basically, things I've found useful after using log4j heavily.  Most of
> them seem fancy and extraneous, until you are dealing with long-running
> production software you have to fix at three in the morning...
>
>
> On Mon, Oct 14, 2013 at 9:02 AM, ilya-stromberg <
> ilya-stromberg-2009 at yandex.ru> wrote:
>
>> On Monday, 14 October 2013 at 13:39:10 UTC, Byron wrote:
>>
>>> ** System logging: syslog and windows event logging support.
>>>
>>
>> +1, add System logging, and use as default windows event logging for
>> windows and syslog for POSIX.
>>
>> And remote log support for syslog to allow send log messages via network.
>>
>> Also, we should support syslog for windows, but in that case user must
>> provide valid syslog daemon (install it for windows or spesify valid
>> network connection).
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puremagic.com/pipermail/digitalmars-d/attachments/20131014/a64eae98/attachment-0001.html>


More information about the Digitalmars-d mailing list