Bug 1386200

Summary: Log all published events
Product: [Community] GlusterFS Reporter: Aravinda VK <avishwan>
Component: eventsapiAssignee: Aravinda VK <avishwan>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainline   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.10.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1402723 (view as bug list) Environment:
Last Closed: 2017-03-06 17:30:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1402723    

Description Aravinda VK 2016-10-18 11:57:53 UTC
Description of problem:
All published events are not logged. Logging all events helps to debug the Webhooks.

Also provide the option to disable logging.

Comment 1 Worker Ant 2016-10-18 11:58:20 UTC
REVIEW: http://review.gluster.org/15674 (eventsapi: Log all published events and provide option to disable logging) posted (#1) for review on master by Aravinda VK (avishwan)

Comment 2 Worker Ant 2016-10-20 10:42:51 UTC
REVIEW: http://review.gluster.org/15674 (eventsapi: Log all published events and provide option to disable logging) posted (#2) for review on master by Aravinda VK (avishwan)

Comment 3 Worker Ant 2016-11-16 10:37:32 UTC
REVIEW: http://review.gluster.org/15674 (eventsapi: Log all published events and provide option to disable logging) posted (#3) for review on master by Aravinda VK (avishwan)

Comment 4 Worker Ant 2016-12-08 09:22:39 UTC
COMMIT: http://review.gluster.org/15674 committed in master by Aravinda VK (avishwan) 
------
commit ff2314995b117b33d81beb6de7b043979c676aeb
Author: Aravinda VK <avishwan>
Date:   Tue Oct 18 16:58:36 2016 +0530

    eventsapi: Log all published events and provide option to disable logging
    
    Log every published event in /var/log/glusterfs/events.log, Disable logging
    using,
    
      gluster-eventsapi config-set disable-events-log true
    
    Also changed "log_level" config name to "log-level"
    
    Change-Id: Ib354be0c4ca999d1ccd01b810d6cd96ebc72bcd4
    BUG: 1386200
    Signed-off-by: Aravinda VK <avishwan>
    Reviewed-on: http://review.gluster.org/15674
    Reviewed-by: Prashanth Pai <ppai>
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>

Comment 5 Shyamsundar 2017-03-06 17:30:20 UTC
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-3.10.0, please open a new bug report.

glusterfs-3.10.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/gluster-users/2017-February/030119.html
[2] https://www.gluster.org/pipermail/gluster-users/