Bug 1104096 - Logging required for nagios gluster plugins
Summary: Logging required for nagios gluster plugins
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gluster-nagios-addons
Version: rhgs-3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Sahina Bose
QA Contact: RHS-C QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-03 09:28 UTC by Sahina Bose
Modified: 2018-08-14 11:17 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-01-30 11:47:58 UTC
Embargoed:

Attachments (Terms of Use)

Description Sahina Bose 2014-06-03 09:28:54 UTC 
Description of problem:

Gluster nagios plugins should log to files for debugging purpose. Currently there's no log and it's difficult to debug issues.

The logs from plugins need to be included in sosreport as well

Version-Release number of selected component (if applicable):
3.0

How reproducible:
Always
Comment 2 RHEL Program Management 2014-06-04 11:35:59 UTC 
Quality Engineering Management has reviewed and declined this request.
You may appeal this decision by reopening this request.
Comment 3 Dusmant 2014-06-05 05:24:52 UTC 
It should be taken after just after Denali release, in ASYNC errata. 
I am moving it to the next release... and keeping this bug opened. Removing blocker flag for Denali release.
Comment 4 Dusmant 2014-10-15 06:51:19 UTC 
It has to be taken in 3.0.3, otherwise debugging customer issues for monitoring would be difficult...
Comment 5 Sahina Bose 2014-11-12 06:32:30 UTC 
http://review.gluster.org/7953
http://review.gluster.org/7955
http://review.gluster.org/7947

- Patches posted to enable logging
Comment 6 Mike McCune 2016-03-28 23:31:34 UTC 
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Comment 7 Sahina Bose 2018-01-30 11:47:58 UTC 
Thank you for your bug report. However, this bug is being closed as it's on a component where no further new development is being undertaken.
Note You need to log in before you can comment on or make changes to this bug.