Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [lttng-dev] [LTTng-UST RFC] Tracepoint Loglevels Specification
Date: Tue, 31 Jan 2012 17:41:19 -0500	[thread overview]
Message-ID: <20120131224119.GA16479@Krystal> (raw)

Hi,

Some early LTTng-UST adopters brought to my attention that the way
tracepoint loglevels are currently specified in LTTng-UST might be too
relax for its own good. If each application define their own loglevel
names/values, it will become difficult to use the loglevels to select
"trace verbosity" in a system-wide manner.

Now that I come to think of it, it might make sense to pre-define a set
of supported loglevels, similarly to syslog(3). However, given that
tracing sometimes targets debug levels that are more fine-grained than
in the case of logs, I would propose to split the "debug" loglevel into
sub-categories. The following loglevel names are just ideas, and
feedback is very welcome.

My current thought is to simply just allow these loglevels. I doubt that
letting application developers specify extra loglevels on top of this
would be that useful, and it would certainly be more confusing.

In the list below, lower numbers means "low verbosity", higher numbers
means "high verbosity, debug-style information".

based on syslog
http://linux.die.net/man/3/syslog
  SUSv2 and POSIX.1-2001. POSIX.1-2001

TRACE_EMERG    0
system is unusable

TRACE_ALERT    1
action must be taken immediately

TRACE_CRIT     2
critical conditions

TRACE_ERR      3
error conditions

TRACE_WARNING  4
warning conditions

TRACE_NOTICE   5
normal, but significant, condition

TRACE_INFO     6
informational message

TRACE_SYSTEM   7
information has system-level scope

TRACE_PROCESS  8
information has process-level scope

TRACE_MODULE   9
information has module (executable/library) scope

TRACE_UNIT     10
information has compilation unit scope

TRACE_CLASS    11
information has class-level scope

TRACE_OBJECT   12
information has object-level scope

TRACE_FUNCTION 13
information has function-level scope

TRACE_PRINTF   14
tracepoint_printf message

TRACE_DEBUG    15
debug-level message

Thoughts ?

Thanks,

Mathieu


-- 
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com



             reply	other threads:[~2012-01-31 22:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-31 22:41 Mathieu Desnoyers [this message]
2012-01-31 22:58 ` Matthew Khouzam
2012-01-31 23:19   ` Mathieu Desnoyers

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=20120131224119.GA16479@Krystal \
    --to=mathieu.desnoyers@efficios.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