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

Ravishankar N ravishankar at redhat.com
Fri Nov 22 10:19:43 UTC 2019

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.


More information about the Gluster-users mailing list