merovingian.log files on our production servers are dominated by these two lines: 2018-03-21 16:55:38 MSG merovingian[23237]: proxying client localhost.localdomain:51502 for database 'test' to mapi:monetdb://path/test/.mapi.sock?database=test 2018-03-21 16:55:38 MSG merovingian[23237]: target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying They account for 90% of the log. Is there a way to reduce verbosity?
Maybe it would be nice to introduce the concept of logging levels in MonetDB (like ALL, DEBUG, INFO, WARN, ERROR, FATAL), so that one can then decide what to log, with a simple configuration option. I would argue the two lines I mention are at level DEBUG. On Thu, 22 Mar 2018 at 17:47 Roberto Cornacchia < roberto.cornacchia@gmail.com> wrote:
merovingian.log files on our production servers are dominated by these two lines:
2018-03-21 16:55:38 MSG merovingian[23237]: proxying client localhost.localdomain:51502 for database 'test' to mapi:monetdb://path/test/.mapi.sock?database=test 2018-03-21 16:55:38 MSG merovingian[23237]: target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying
They account for 90% of the log.
Is there a way to reduce verbosity?
participants (1)
-
Roberto Cornacchia