Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: jeremie.galarneau@efficios.com (Jérémie Galarneau)
Subject: [lttng-dev] Using lttng for traces and (in-process) logging
Date: Fri, 10 Aug 2018 12:23:20 -0400	[thread overview]
Message-ID: <CA+jJMxuvkd2=OM8G_NGjgGzeZTL6dEzq=DcH-XLWx8rQfesQYw@mail.gmail.com> (raw)
In-Reply-To: <CADYdroNy37NmavhVhMaUkR+k9+rJLc_6C3PoXq1rx_ZMwX=VtQ@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]

Hi,

I can see how this could be approximated by configuring a "live" tracing
session (i.e. you would see the log as they are produced), but there is
no way, currently, to serialize the events to stdout/stderr from the
application itself.

Maybe I misunderstood your question. Let me know.

Jérémie

On 6 August 2018 at 18:42, Norbert Lange <nolange79 at gmail.com> wrote:
> 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.
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev



-- 
Jérémie Galarneau
EfficiOS Inc.
http://www.efficios.com


  reply	other threads:[~2018-08-10 16:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-06 22:42 Norbert Lange
2018-08-10 16:23 ` Jérémie Galarneau [this message]
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='CA+jJMxuvkd2=OM8G_NGjgGzeZTL6dEzq=DcH-XLWx8rQfesQYw@mail.gmail.com' \
    --to=jeremie.galarneau@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