[erlang-questions] Should we deprecate or modernize log_mf_h and rb?

[Richard Carlsson]

Yeah, the main thing the rotation mechanism is missing  in our handler as
well is renumbering of existing files; it also simply increments the number
as it goes, and you have to sort on timestamps to see which one is the
latest. Hence, I can't recommend it as is unless you don't mind that sort
of bother. On the other hand, clear text logs are nice. Somehow, there's
always been something more important to do than improve the log numbering,
but that's how it is.

        /Richard


Den fre 15 feb. 2019 kl 22:09 skrev Andrew Thompson <andrew@REDACTED>:

> On Fri, Apr 08, 2016 at 02:36:37PM +0200, Siri Hansen wrote:
> > Thanks for the feedback, everyone!
> >
> > We have now decided not to remove log_mf_h and rb. Instead there will be
> > some work done to modernize these tools.
>
> The big problem we had with these at Basho (RIP) was that customers had
> no idea how the log files worked because it's very different to
> traditional UNIX logging. Usually you have things like app.log,
> app.log.0, ... app.log.N and the number indicates their age. log_mf has
> a weird index file where the active log file is encoded as a decimal
> value (not ASCII, IIRC). This is very confusing for everyone who is not
> an Erlang user (maybe even for them judging by this thread).
>
> The main thing I'd like to see improve is the ergonomics. Make it work
> more like a sysadmin would expect, have the newest log file be .0 and
> dump the index. Every time you overflow move the files around to reflect
> that.
>
> Andrew
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20190215/3ffe8382/attachment.htm>