public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Bligh <mbligh@google.com>
To: Lucas Meneghel Rodrigues <lmr@redhat.com>
Cc: Michael Goldish <mgoldish@redhat.com>,
	Autotest mailing list <autotest@test.kernel.org>,
	KVM List <kvm@vger.kernel.org>
Subject: Re: [Autotest] Log message format in KVM-Autotest
Date: Mon, 8 Jun 2009 11:15:24 -0700	[thread overview]
Message-ID: <33307c790906081115g543023c9o6d1b048c290a7ae2@mail.gmail.com> (raw)
In-Reply-To: <1244466195.2849.37.camel@localhost.localdomain>

if it's specific to one test or whatever, you could also just put it
inside the message?
Possibly with your own wrapper function around the logging?

On Mon, Jun 8, 2009 at 6:03 AM, Lucas Meneghel Rodrigues<lmr@redhat.com> wrote:
> On Mon, 2009-06-08 at 06:35 -0400, Michael Goldish wrote:
>> Hi Lucas,
>>
>> Before the merge with Autotest we used kvm_log.py to log formatted messages.
>> Each message contained the current test's 'shortname' (e.g. Fedora.8.32.install), the current date and time (down to a 1 sec resolution) and the message itself. In addition, debug messages contained the name of the calling function, e.g.
>> remote_login: Trying to login...
>>
>> What is the preferred way of obtaining this functionality using the new logging system inside Autotest? Should we define our own logging Handler for the KVM test in kvm.py, along with our own Formatter, or should we use logging.config.fileConfig(), or is there another preferred way?
>> I'm particularly interested in printing the name of the caller in debug messages. This feature makes debugging easier and improves overall readability of the logs. (Obviously we can manually hardcode the name of the current function into every debug message, but that doesn't seem like a good solution.)
>
> The logging system can be configured to display several LogRecord
> attributes, they are documented under
>
> http://docs.python.org/library/logging.html#formatter-objects
>
> %(funcName)s is the name of the function issuing the logging call, so
> that's what we are looking to mirror the wanted functionality.
>
> Creating a logging Handler with a formatter on its own is a possibility,
> although we can propose adding the name of the function to the file
> format being used by autotest. There's allways the concern that an
> excess of information may clutter the logs.
>
> Right now, for files we use the following format:
>
> http://autotest.kernel.org/browser/trunk/client/debug_client.ini
>
> [formatter_file_formatter]
> format=[%(asctime)s %(levelname)-5.5s %(module)s] %(message)s
> datefmt=%m/%d %H:%M:%S
>
> The formatter we're using for the logs contain a timestamp, the debug
> level name and the module (source file except the .py extension). I
> believe this makes debugging easy enough without cluttering too much the
> logs. Do you think the caller name would be an interesting addition even
> considering the above?
>
>
>> Thanks,
>> Michael
> --
> Lucas Meneghel Rodrigues
> Software Engineer (QE)
> Red Hat - Emerging Technologies
>
> _______________________________________________
> Autotest mailing list
> Autotest@test.kernel.org
> http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
>

  reply	other threads:[~2009-06-08 18:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <299034493.1415451244457314604.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-06-08 10:35 ` Log message format in KVM-Autotest Michael Goldish
2009-06-08 13:03   ` Lucas Meneghel Rodrigues
2009-06-08 18:15     ` Martin Bligh [this message]
2009-06-08 19:17       ` [Autotest] " Lucas Meneghel Rodrigues
     [not found] <16636675.1504651244491486554.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-06-08 20:05 ` Michael Goldish

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=33307c790906081115g543023c9o6d1b048c290a7ae2@mail.gmail.com \
    --to=mbligh@google.com \
    --cc=autotest@test.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=lmr@redhat.com \
    --cc=mgoldish@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox