Pre-assign fixed loglevels
authorMathieu Desnoyers <mathieu.desnoyers@efficios.com>
Wed, 1 Feb 2012 22:54:50 +0000 (17:54 -0500)
committerMathieu Desnoyers <mathieu.desnoyers@efficios.com>
Wed, 1 Feb 2012 22:54:50 +0000 (17:54 -0500)
commit75c5ad79cbdc0b7d0579ccd1c97902ded5bdc08a
tree75c1768746f1fd96a8ad03702d5ef01e64e51120
parent51c5df09105025dc696ac5c89a819b73cc52b687
Pre-assign fixed loglevels

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.

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".

Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
include/lttng/tracepoint.h
include/lttng/ust-tracepoint-event.h
tests/demo/ust_tests_demo.h
tests/demo/ust_tests_demo2.h
tests/demo/ust_tests_demo3.h
This page took 0.025257 seconds and 4 git commands to generate.