From: nolange79@gmail.com (Norbert Lange)
Subject: [lttng-dev] Using lttng for traces and (in-process) logging
Date: Tue, 7 Aug 2018 00:42:11 +0200 [thread overview]
Message-ID: <CADYdroNy37NmavhVhMaUkR+k9+rJLc_6C3PoXq1rx_ZMwX=VtQ@mail.gmail.com> (raw)
Hello,
since lttng would make for a decent logger, is it possible to create a
own tracepoint provider and channel and acess it in the very same
process thats traced?
the log entries would need to be accessible directly to support some
existing schemes for manipulating (interpolating to a different
clock-source), forwarding and storing them.
eg. I would like to access the logs and other traces with the normal
lttng tools, but also be able to get a copy of the logs directly from
the process generating them.
next reply other threads:[~2018-08-06 22:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-06 22:42 Norbert Lange [this message]
2018-08-10 16:23 ` Jérémie Galarneau
2018-08-10 20:16 ` Norbert Lange
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='CADYdroNy37NmavhVhMaUkR+k9+rJLc_6C3PoXq1rx_ZMwX=VtQ@mail.gmail.com' \
--to=nolange79@gmail.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