All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers via lttng-dev <lttng-dev@lists.lttng.org>
To: Sergei Dyshel <qyron.private@gmail.com>
Cc: lttng-dev <lttng-dev@lists.lttng.org>
Subject: Re: Have live session and rotation together
Date: Wed, 22 Apr 2020 15:00:39 -0400 (EDT)	[thread overview]
Message-ID: <2090780417.64200.1587582039964.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <CAAeL1MEWf=qo59pPCOEcqOm_obg3w0v=LHSmcZtfdt8=QM_vOA@mail.gmail.com>

----- On Apr 22, 2020, at 2:18 PM, Sergei Dyshel qyron.private@gmail.com wrote:

> Thanks! I really missed this feature somehow.
> 
> However I see that passing 0 as "tracefile size" will remove size
> limitation. Is it possible to disable CTF trace writing altogether?

No, because the relay daemon uses the on-disk files as intermediate
storage between the receiving end and the part interacting with live
viewers.

Note that https://bugs.lttng.org/issues/1182 tracks a known issue
where the relay daemon mishandles tracefile-count == 0 and tracefile-size != 0.
It has not been a priority to fix this issue so far.

Thanks,

Mathieu


> --
> Regards,
> Sergei Dyshel
> 
> On Wed, Apr 22, 2020 at 2:15 AM Mathieu Desnoyers
> <mathieu.desnoyers@efficios.com> wrote:
>>
>> ----- On Apr 21, 2020, at 5:37 PM, Sergei Dyshel qyron.private@gmail.com wrote:
>>
>> [...]
>> >
>> >> Considering that there are few compelling use-cases for using both
>> >> features together, and no customer have expressed interest in this,
>> >> it is not part of our roadmap.
>> >
>> > Here is my case: I'm using LTTNG for continuous tracing during the
>> > whole system timeline,
>> > generating pretty big volume of traces.
>> >
>> > I'm using live and session and Babeltrace2 plugin which converts
>> > processes these traces,
>> > converts them to text and stores them
>> > in some text file to which I apply "logrotate" so that old traces are
>> > archived when needed.
>> >
>> > However, as I see, "lttng-relayd" also writes binary traces in CTF
>> > from to some directory, never discarding old traces. So assuming
>> > system long runtime this directory is going to eat all the free space
>> > sometime?! Rotation would allow me to discard old archives just as
>> > "logrotate" does. How else can I discard old CTF files?
>>
>> The feature you need is called "tracefile rotation", with the channel
>> attributes "tracefile count" and "tracefile size". It was implemented at
>> the same time as the live mode for exactly the purpose you describe.
>>
>> See https://lttng.org/docs/#doc-tracefile-rotation for more information.
>>
>> Thanks,
>>
>> Mathieu
>>
>> --
>> Mathieu Desnoyers
>> EfficiOS Inc.
> > http://www.efficios.com

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com

      reply	other threads:[~2020-04-22 19:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-20 20:17 Have live session and rotation together Sergei Dyshel via lttng-dev
2020-04-21 14:23 ` Mathieu Desnoyers via lttng-dev
2020-04-21 21:37   ` Sergei Dyshel via lttng-dev
2020-04-21 23:15     ` Mathieu Desnoyers via lttng-dev
2020-04-22 18:18       ` Sergei Dyshel via lttng-dev
2020-04-22 19:00         ` Mathieu Desnoyers via lttng-dev [this message]

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=2090780417.64200.1587582039964.JavaMail.zimbra@efficios.com \
    --to=lttng-dev@lists.lttng.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=qyron.private@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.