From: david.lindstrom@percepio.se (David Lindström)
Subject: [lttng-dev] Tagging traces with arbitrary data (as in custom metadata)
Date: Tue, 5 Nov 2013 15:15:14 +0100 [thread overview]
Message-ID: <C62A2692A7474EDFAB0AD54DA97D77E8@DVDMANDT5> (raw)
Hi, I was wondering if there?s a way to tag a trace with some additional information. A general example would be to include a description of the current experiment. One way to do this currently would be to create a custom lttng-message application with some UST tracepoint and then just log that to a separate channel, but that would be pretty ugly. It would be much cleaner to insert extra fields into the metadata stream. Is something like that possible in current versions of LTTng and/or would it be possible to add it for a future version?
Mvh
David Lindstr?m
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20131105/7874caa6/attachment.html>
next reply other threads:[~2013-11-05 14:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 14:15 David Lindström [this message]
2013-11-05 14:20 ` Mathieu Desnoyers
2013-11-05 14:49 ` [lttng-dev] Tagging traces with arbitrary data (as in custommetadata) David Lindström
2014-02-03 16:09 ` 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=C62A2692A7474EDFAB0AD54DA97D77E8@DVDMANDT5 \
--to=david.lindstrom@percepio.se \
/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