Re: [Kimchi-devel] [RFC] [Wok] Feature: User Activity Log

Yes, it does. What about the input fields for the advanced search?

And the Download button, is the placement correct or should we put a button on the top?

Samuel -----Original Message----- From: Aline Manera [mailto:alinefm@linux.vnet.ibm.com] Sent: quarta-feira, 17 de fevereiro de 2016 11:40 To: Samuel Henrique De Oliveira Guimaraes <samuel.guimaraes(a)eldorado.org.br>; luciojhc(a)linux.vnet.ibm.com; Walter Niklaus <niklaus(a)linux.vnet.ibm.com>; Kimchi Devel <kimchi-devel(a)ovirt.org&gt; Subject: Re: [Kimchi-devel] [RFC] [Wok] Feature: User Activity Log Hi Samuel, Thanks for the mockups! The "Advanced Search" should be displayed inside the "User Activity Log" element. + User Activity Log | Advanced Search | | Filter| The "Advanced Search" can continue to be an expanded area but move it inside the "User Activity Log". Does that make sense? Regards, Aline Manera On 02/16/2016 11:22 AM, Samuel Henrique De Oliveira Guimaraes wrote: > Hi team, > > I've created two wireframes for the User Activity Log. One features the default jQuery Bootgrid with inline filter (I've changed the label to "filter" to match other screens and make it easier for the user to distinguish filter from search) and another one features the collapsed Advanced Search panel. > > For now I have used default text input fields but I believe we can change Requests and Plugins for select inputs (using Selectpicker). We can also use Typeahead.js when user starts typing the usernames and a Datepicker for Date. I was thinking for the Date column maybe we could use a date range instead of a single date search. In this case we would have another column in Advanced Search with another datepicker input (From - To approach). > > BTW, if User Activity Log screen will be a part of Wok, then what should the navbar look like when this page is active? Should we hide the navbar? Create another first-level element for this page? Display it next to User and Help drop-downs? > > Regards, > Samuel > > -----Original Message----- > From: kimchi-devel-bounces(a)ovirt.org > [mailto:kimchi-devel-bounces@ovirt.org] On Behalf Of Lucio Correia > Sent: quarta-feira, 10 de fevereiro de 2016 14:49 > To: Walter Niklaus <niklaus(a)linux.vnet.ibm.com>; Aline Manera > <alinefm(a)linux.vnet.ibm.com>; Kimchi Devel <kimchi-devel(a)ovirt.org&gt; > Subject: Re: [Kimchi-devel] [RFC] [Wok] Feature: User Activity Log > > On 10-02-2016 13:58, Walter Niklaus wrote: >> This is a great new feature: +1 >> >> I have one question on the backend side section. >> >> On 10.02.2016 15:36, Aline Manera wrote: > ... >>>> Backend design >>>> -------------- >>>> - Define activity texts for each currently implemented activity of >>>> all plugins >>>> - Implement method to retrieve the activity texts in Wok and all >>>> plugins >>>> - Log events to a JSON file in the host file system. Each user >>>> request received by Wok will generate an entry in the respective >>>> log file. Fields to be saved for each entry: plugin, datetime, >>>> user, request type (PUT, POST, GET, DELETE), activity text (i.e. >>>> "create guest 'vm-sample'") >>>> - Implement code for retrieving and filtering log events by the >>>> fields above >>>> >> Are we planning with any archiving or wrap-around feature for the >> JSON file ? If we are simply accumulating the entries in the same >> file, I'm concerned that at a certain point we may end with a huge >> file and run into performance issues. >> As a start we could define a simple wrap-around mechanism and leave >> the responsibilty for archiving to the administrator. > The plan is to have file size limit and log rotation. There are some logging facilities in Python which allow for that. > > -- > Lucio Correia > Software Engineer > IBM LTC Brazil > > _______________________________________________ > Kimchi-devel mailing list > Kimchi-devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/kimchi-devel