Re: [gentoo-soc] GSoC 2013: Log collector

[Brian Dolbec]

On Mon, 2013-04-29 at 02:48 +0100, Antanas Uršulis wrote:
> - the collector & analyser:
> --- receives logs over some protocol
> --- should be able to group logs (receive several log files for a
> failing package and keep them together) (this, depending on the
> implementation, might be part of the portage integration)
> --- matches each line against a regexp, we can look into something
> more extensible if required
> --- organises the files by hostname and submits them to the storage backend
>
> - the storage backend:
> --- I could start with Amazon's AWS and then move to something
> standalone (how much data is there to store, actually? 1/10/100 GB?
> and how large can a single log file become?)
> --- keeps the logs and also a simple database that would hold
> information about the log groups (package, date, links to log files,
> etc.)
>
> - the frontend:
> --- displays a list of packages that have matches
> --- should be integrated with bugzilla; one can see open bugs for a
> selected package, and also file a new bug
> --- should be password protected
>

If you would like a gtk frontend for parsing logs, porthole's terminal
is pretty much a ready to use app which already parses portage output,
separates out error and warning messages to separate views. The
separated warnings, etc. make it easy to peruse to find the relevant
errors, double-clicking on one brings you to the place in the main log
where the error occurred.  There you can move through and find the cause
if it is shown.  It has been my intention for years to separate it from
the package browser.  If you are interested in all or part of the code.

http://sourceforge.net/p/porthole/code/ci/master/tree/porthole/terminal/

P.S. This portion of the terminal code was done long before portage had
the current logging capability.
-- 
Brian Dolbec <dolsen@g.o>