Re: [Gluster-Maintainers] [Gluster-devel] Modifying gluster's logging mechanism

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 22/11/19 3:13 pm, Barak Sason Rofman wrote:
This is actually one of the main reasons I wanted to bring this up for discussion - will it be fine with the community to run a dedicated tool to reorder the logs offline?

I think it is a bad idea to log without ordering and later relying on an external tool to sort it.  This is definitely not something I would want to do while doing test and development or debugging field issues.  Structured logging  is definitely useful for gathering statistics and post-processing to make reports and charts and what not,  but from a debugging point of view, maintaining causality of messages and working with command line text editors and tools on log files is important IMO.

I had a similar concerns when  brick multiplexing feature was developed where a single log file was used for logging all multiplexed bricks' logs.  So much extra work to weed out messages of 99 processes to read the log of the 1 process you are interested in.

Regards,
Ravi

________

Community Meeting Calendar:

APAC Schedule -
Every 2nd and 4th Tuesday at 11:30 AM IST
Bridge: https://bluejeans.com/441850968

NA/EMEA Schedule -
Every 1st and 3rd Tuesday at 01:00 PM EDT
Bridge: https://bluejeans.com/441850968

Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users




[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux