Bug 1087947 - Feature request: configurable error reporting hook script
Summary: Feature request: configurable error reporting hook script
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: GlusterFS
Classification: Community
Component: logging
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-15 16:34 UTC by Justin Dossey
Modified: 2018-11-20 09:37 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-11-20 09:08:47 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Justin Dossey 2014-04-15 16:34:54 UTC
When GlusterFS detects a serious problem with a brick, it logs a message and the output of gluster volume status changes.  

It would be awfully handy to be able to configure a hook script that is fired on brick failure (or perhaps other issues) so administrators are alerted immediately.  

Such a script might fire an SNMP trap or send an e-mail to the operations team, and it would be up to the customer to implement it as appropriate in their environment.  

The current alternative (log parsing, gluster volume status parsing) is comparatively error-prone.

Comment 1 Niels de Vos 2014-11-27 14:45:20 UTC
Feature requests make most sense against the 'mainline' release, there is no ETA for an implementation and requests might get forgotten when filed against a particular version.

Comment 2 Vijay Bellur 2018-11-20 09:37:06 UTC
Migrated to github:

https://github.com/gluster/glusterfs/issues/588

Please follow the github issue for further updates on this bug.


Note You need to log in before you can comment on or make changes to this bug.