+++ This bug was initially created as a clone of Bug #1386200 +++ Description of problem: All published events are not logged. Logging all events helps to debug the Webhooks. Also provide the option to disable logging. --- Additional comment from Worker Ant on 2016-10-18 07:58:20 EDT --- 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) --- Additional comment from Worker Ant on 2016-10-20 06:42:51 EDT --- 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) --- Additional comment from Worker Ant on 2016-11-16 05:37:32 EST --- 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) --- Additional comment from Worker Ant on 2016-12-08 04:22:39 EST --- 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>
REVIEW: http://review.gluster.org/16067 (eventsapi: Log all published events and provide option to disable logging) posted (#1) for review on release-3.9 by Aravinda VK (avishwan)
This bug is getting closed because GlusterFS-3.9 has reached its end-of-life [1]. Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS. If this bug still exists in newer GlusterFS releases, please open a new bug against the newer release. [1]: https://www.gluster.org/community/release-schedule/