From: chid1989@gmail.com (Chidhu R)
Subject: [lttng-dev] Trace to console
Date: Thu, 23 Apr 2015 11:58:57 -0700 [thread overview]
Message-ID: <CAL1ZhOPtw4iPv0tiEtd4uMjt1sRFFdYSztNDGywD-kLDO-v-hg@mail.gmail.com> (raw)
In-Reply-To: <CAL1ZhOO=w0rCAcEf5StxWe1tk95Vy-L9WVwxjbSxQXKO7L0BEw@mail.gmail.com>
Also, is there a way to redirect all tracepoints to console instead of
selective?
On Thu, Apr 23, 2015 at 11:14 AM, Chidhu R <chid1989 at gmail.com> wrote:
> Thanks Jeremie.
>
> On Tue, Apr 21, 2015 at 5:27 PM, J?r?mie Galarneau <
> jeremie.galarneau at efficios.com> wrote:
>
>> Hi Chidhu,
>>
>> LTTng does not support selective output of tracepoints to the console.
>> The closest thing I can recommend is using the "live" mode locally.
>>
>> J?r?mie
>>
>> On Mon, Apr 20, 2015 at 3:58 PM, Chidhu R <chid1989 at gmail.com> wrote:
>> > Hello,
>> >
>> > I was looking for a way to trace to console rather than save to disk /
>> > stream. I read about lttng tracef feature. But it does not include the
>> wide
>> > range of benefits brought by tracepoints. So what I want is to use the
>> > tracepoints and trace to console instead. For example, if there are 5
>> > tracepoint events, I want to trace 3 of them to console and let the
>> other go
>> > the disk or whatever. How to achieve this.
>> >
>> > Thanks
>> > Chid
>> >
>> > _______________________________________________
>> > lttng-dev mailing list
>> > lttng-dev at lists.lttng.org
>> > http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>> >
>>
>>
>>
>> --
>> J?r?mie Galarneau
>> EfficiOS Inc.
>> http://www.efficios.com
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20150423/1c75aca1/attachment.html>
next prev parent reply other threads:[~2015-04-23 18:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 19:58 Chidhu R
2015-04-22 0:27 ` Jérémie Galarneau
2015-04-23 18:14 ` Chidhu R
2015-04-23 18:58 ` Chidhu R [this message]
2015-04-23 19:01 ` Chidhu R
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=CAL1ZhOPtw4iPv0tiEtd4uMjt1sRFFdYSztNDGywD-kLDO-v-hg@mail.gmail.com \
--to=chid1989@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