Bug 880576 - [RHS-C] Improve the "Events" log time upto second/microsecond granularity
Summary: [RHS-C] Improve the "Events" log time upto second/microsecond granularity
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhsc
Version: 2.0
Hardware: All
OS: All
medium
medium
Target Milestone: ---
: ---
Assignee: Sahina Bose
QA Contact: RHS-C QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-27 11:22 UTC by Prasanth
Modified: 2015-05-15 17:54 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-13 10:33:16 UTC
Embargoed:


Attachments (Terms of Use)
Events_logs (111.89 KB, image/png)
2012-11-27 11:22 UTC, Prasanth
no flags Details

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 .


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