Sure, that sounds like a good idea. Count me in. ----- Original Message ----- From: "Sean Dague" <s...@dague.net> To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Sent: Wednesday, November 6, 2013 5:31:12 PM Subject: Re: [openstack-dev] A Tool for Making OpenStack Log Reading a Bit Easier
First, very cool tool, nice work! I wonder if it's reasonable (or interesting) to take these approaches and bring them into os-loganalyze. That would mean there was common parsing routines, and then we would just call out to different functions if were were trying to do HTML or ANSI coloring. I personally live so often off the weblogs that I honestly hadn't thought about the local case, which would be definitely interesting. It would also be really great if adding semantics to one use did it for the other as well, so people would see the same output when they were looking at test failures as when they were doing local development. If you are interested in trying to join efforts there, let me know. On Wed, Nov 6, 2013 at 9:36 AM, Joe Gordon <joe.gord...@gmail.com> wrote: > > > > On Wed, Nov 6, 2013 at 9:10 AM, Clint Byrum <cl...@fewbar.com> wrote: >> >> I often use ccze to look at logs. It has some built in things like >> coloring the words "warn" or "warning" yellow and "error" red. It would >> be great to have this filter added as another ccze plugin. >> > > Sean Dague, wrote a really slick tool for logs.openstack.org that is > similar: > > http://git.openstack.org/cgit/openstack-infra/os-loganalyze/tree/README.rst > > http://logs.openstack.org/98/54198/7/check/check-tempest-devstack-vm-neutron/a153156/logs/screen-q-svc.txt.gz?level=TRACE > >> >> Excerpts from Solly Ross's message of 2013-11-06 05:58:02 +0800: >> > Hello All, >> > The other day, I was reading through a debug-level OpenStack log, and >> > came to the realization that reading OpenStack debug-level logs was >> > difficult, to say the least -- they can be very busy, and it is hard to >> > quickly filter out relevant information. Thus, I wrote a little Perl >> > script >> > to make reading dense debug-level logs a bit easier: >> > https://github.com/DirectXMan12/os_log_prettifier. I figured that I'd >> > share >> > it with other people. Basically, the script highlights certain key details >> > using color and bolding (via ANSI control codes), and can filter lines >> > based >> > on subject (in the form of 'x.y.z') or message type, using regular >> > expressions. I hope people find it useful! >> > >> > Best Regards, >> > Solly Ross >> > >> >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Sean Dague http://dague.net _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
