The option should be just 'logsize' - the gluster components do not send anything via syslog afaik.

AFAIK, a sosreport will collect all files in /var/log/glusterfs without restriction. This can result in extremely large sosreports (20GB in a current case) that are difficult to deliver and retrieve, and can cause significant latency in supporting a customer.

That's correct. This is a trivial change to add a 'logsize' parameter and switch to the addCopySpecLimit() API. Changes of this type are considered bugs rather than feature requests in sos since they have major usability impacts.

Because of the way that gluster structures its logs I've applied limiting separately to each of the (non-rotated) default log paths:

         # all_logs takes precedence over logsize
        if not self.getOption("all_logs"):
            limit = self.getOption("logsize")
        else:
            limit = 0

        if limit:
            # collect logs last as some of the other actions create log entries
            self.addCopySpecLimit("/var/log/glusterfs/cli.log", limit)
            self.addCopySpecLimit("/var/log/glusterfs/*.vol.log", limit)
            self.addCopySpecLimit("/var/log/glusterfs/gluster-lock.log", limit)
            self.addCopySpecLimit("/var/log/glusterfs/glustershd.log", limit)
            self.addCopySpecLimit("/var/log/glusterfs/nfs.log", limit)
            self.addCopySpecLimit("/var/log/glusterfs/quota-crawl.log", limit)
            self.addCopySpecLimit("/var/log/glusterfs/quotad.log", limit)
            self.addCopySpecLimit("/var/log/glusterfs/quotad-mount-*.log", limit)
            self.addCopySpecLimit("/var/log/glusterfs/status.log", limit)
            self.addCopySpecLimit("/var/log/glusterfs/bricks/*.log", limit)

This considerably reduces the size of these paths for a typical installation:

# sosreport -v --batch --debug -o gluster
[...]
# du -ch bmr-rhel6-vm1-2014061917231403195010/var/log/glusterfs/
12K     bmr-rhel6-vm1-2014061917231403195010/var/log/glusterfs/bricks
40K     bmr-rhel6-vm1-2014061917231403195010/var/log/glusterfs/
40K     total


The old behaviour may be obtained by passing '-k gluster.all_logs' or '-k gluster.logsize=0':

# sosreport -v --batch --debug -o gluster -k gluster.all_logs
[...]
# du -ch bmr-rhel6-vm1-2014061917261403195160/var/log/glusterfs/
60K     bmr-rhel6-vm1-2014061917261403195160/var/log/glusterfs/bricks
292K    bmr-rhel6-vm1-2014061917261403195160/var/log/glusterfs/
292K    total

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-1528.html