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

Robert Virding rvirding@REDACTED
Sat Apr 2 18:34:58 CEST 2016

Would it be possible to split out the binary data so it could be used as an
option with the rotating files? I don't know if this would be interesting
as such but you colud maybe still use rb to view the logs.

Another benefit of doing this would be to break out the formatting of the
log messages outside of the erlang system. This would give all the speed
benefits and still provide text logs for those who want it. It would also
make it easier to provide different text formats.


On 2 April 2016 at 09:05, Vance Shipley <vances@REDACTED> wrote:

> On Apr 1, 2016 12:44 PM, "Siri Hansen" <erlangsiri@REDACTED> wrote:
> > Are you using log_mf_h (e.g. by setting environment variables
> 'error_logger_mf_*' in sasl) and rb?
> Yes, this is part of my default configuration for embedded systems.
> > If so, why - is it the log rotation or the binary logging (or both) that
> you are really after?
> Both.
> > Have you considered alternative tools?
> I've considered application specific versions of this scheme.
> On Sat, Apr 2, 2016 at 1:23 AM, Robert Raschke <rtrlists@REDACTED>
> wrote:
> > Unfortunately, straight logged binary data and formatting it at read
> time appears to be majorly out of fashion :-(
> Stupidly so IMHO.  I often see systems with a mission of moving
> massive amounts of message traffic logging data orders of magnitude
> larger than the size of the actual message.  Doing so naively results
> in the servers spending much more time logging than doing the work
> they're intended to do.  Logging is important and at this rate it
> costs real money to accomplish so it deserves to be engineered
> sensibly.  My rational is that where a gen_fsm is spawned for each
> transaction it should simply do it's work and before terminating send
> it's State variable term, usually a record, directly to a log handler
> (e.g. disk_log).  To have the worker for traffic doing string
> processing for an human to possibly read a long time later makes no
> sense.  Log binary data to disk and format just the data requested, at
> request time, formatted for the requestor.
> --
>      -Vance
> _______________________________________________
> 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/20160402/8dc2326d/attachment.htm>

More information about the erlang-questions mailing list