Bug 1575908 - [RFE] AuditLog Feature
Summary: [RFE] AuditLog Feature
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: gluster-block
Version: cns-3.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: OCS 3.11
Assignee: Bhumika Goyal
QA Contact: Rachael
Depends On:
Blocks: 1632821
TreeView+ depends on / blocked
Reported: 2018-05-08 09:14 UTC by Bhumika Goyal
Modified: 2018-10-24 04:54 UTC (History)
12 users (show)

Fixed In Version: gluster-block-0.2.1-27.el7rhgs
Doc Type: Enhancement
Doc Text:
The CLI audit logs have been added to capture every CLI command and its response. This makes logs more detailed and easier to understand the gluster-block CLI operations history, which will improve debugability.
Clone Of:
Last Closed: 2018-10-24 04:52:58 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:2987 0 None None None 2018-10-24 04:54:38 UTC

Description Bhumika Goyal 2018-05-08 09:14:57 UTC
Description of problem:

Right now there is no mechanism that records the requests and responses that the gluster-block daemon receives. And therefore, it becomes difficult to troubleshoot the bugs.

Changes needed: 

Develop a feature that will record the response status and the requests received by gluster-block daemon for the operations Create/Delete/Modify. The logs will record  the request, response status(success/failure) and the response string received from the servers.

The logging format is:
In case of success:
[time] : command string at CLI: SUCCESS: Response string

In case of failure:
[time] : command string at CLI: FAILURE: Response string

Design discussion link:

Comment 9 Anjana KD 2018-10-12 05:25:14 UTC
Updated the changes.

Comment 11 errata-xmlrpc 2018-10-24 04:52:58 UTC
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.


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