Bug 880576

Summary: [RHS-C] Improve the "Events" log time upto second/microsecond granularity
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Prasanth <pprakash>
Component: rhscAssignee: Sahina Bose <sabose>
Status: CLOSED WONTFIX QA Contact: RHS-C QE <rhsc-qe-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.0CC: dpati, mmahoney, rhs-bugs, sdharane, ssampat
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-13 10:33:16 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:
Attachments:
Description Flags
Events_logs none

Description Prasanth 2012-11-27 11:22:05 UTC
Created attachment 652624 [details]
Events_logs

Version-Release number of selected component (if applicable): rhsc-2.1-qa18.el6ev.noarch


Description of problem:

In "Events", the current time is in the format: YYYY-MM-DD, Hrs:MM <event>

EX: 2012-Nov-27, 07:07 	User admin@internal logged in

Also, see attached.

At present, the Events have a "Basic View" and an "Advanced View". But, for a troubleshooting purpose from the UI. I don't think either of this is really useful now for a system administrator, as it doesn't show any detailed events that has happened within the 60sec time frame. 

Currently, the Glusterfs logs do have time upto microsecond granularity.


a.) Consider adding either the second (preferred) or microsecond (if possible) logging for the Events.

b.) Apart from the "Basic View" and "Advanced View", we may also consider adding one more view (say: Debug mode) which shows the detailed logs with time upto microsecond granularity.

I think, this will be really useful for any RHS-C administrators for a first level of troubleshooting using the UI itself, in case of any issues, without actually having the need of checking the back-end engine server .