Description of problem:
Many monitoring/reporting solutions run 'gluster volume heal $volname info' and its related subcommands very frequently (even once every minute), leading to unnecessary filling up of the glfsheal logs. (See downstream BZs 1579293 and 1631851 for instance). The main intention of running these commands is to process/consume the output displayed on stdout/xml format and not really the gluster client logs which glfsheal (which is gfapi based) generates under /var/log/glusterfs/glfsheal*.
Hence it is useful to have a --nolog option which will prevent the incessant logging.
Note that these logs are VERY helpful when debugging when heal-info is unresponsive/hung/disconnected from bricks or when running split-brain resolution commands. So the default log level is still kept at GF_LOG_INFO and is changed to GF_LOG_NONE only when the command is invoked with the --nolog flag.
REVIEW: https://review.gluster.org/21501 (glfsheal: add a '--nolog' option) posted (#1) for review on master by Ravishankar N
REVIEW: https://review.gluster.org/21501 (glfsheal: add a '--nolog' flag) posted (#5) for review on master by Pranith Kumar Karampuri
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-6.0, please open a new bug report.
glusterfs-6.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.