From: qyron.private@gmail.com (Sergei Dyshel)
Subject: [lttng-dev] Have live session and rotation together
Date: Wed, 22 Apr 2020 00:37:05 +0300 [thread overview]
Message-ID: <CAAeL1ME-1B6uLf9iGVWcpA=5MqAMLaCoq+eLkDCsd=GpXy5gJg@mail.gmail.com> (raw)
In-Reply-To: <211031090.61650.1587478983634.JavaMail.zimbra@efficios.com>
> I do not think this statement is factually correct. I recall that session
> rotation was available for sessions being streamed over the network. What
> makes you think otherwise ?
I think I tried to enable rotation for network streaming session and
failed but I don't have
2.11 version currently to reproduce this.
> 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?
--
Regards,
Sergei Dyshel
On Tue, Apr 21, 2020 at 5:23 PM Mathieu Desnoyers
<mathieu.desnoyers at efficios.com> wrote:
>
> ----- On Apr 20, 2020, at 4:17 PM, lttng-dev lttng-dev at lists.lttng.org wrote:
>
> > Hi all,
> >
> > When creating live session (lttng create --live) I can not enable rotation:
> >
> > # lttng enable-rotation --size=10M
> > Error: Failed to enable size-based rotation schedule on session BX
>
> This is indeed the expected behavior.
>
> >
> > In LTTNG 2.12 rotation is supported for network streaming mode but it
> > was not yet supported in 2.11.
>
> I do not think this statement is factually correct. I recall that session
> rotation was available for sessions being streamed over the network. What
> makes you think otherwise ?
>
> >
> > Is there architectural reasons why we can't have live session with rotation?
> > Or is it just not implemented yet? In that case in what version is it
> > expected to appear?
>
> It is not impossible design-wise, but would make the implementation much more
> complex and require a very significant testing effort.
>
> 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.
>
> Thanks,
>
> Mathieu
>
> --
> Mathieu Desnoyers
> EfficiOS Inc.
> http://www.efficios.com
next prev parent reply other threads:[~2020-04-21 21:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 20:17 Sergei Dyshel
2020-04-21 14:23 ` Mathieu Desnoyers
2020-04-21 21:37 ` Sergei Dyshel [this message]
2020-04-21 23:15 ` Mathieu Desnoyers
2020-04-22 18:18 ` Sergei Dyshel
2020-04-22 19:00 ` 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='CAAeL1ME-1B6uLf9iGVWcpA=5MqAMLaCoq+eLkDCsd=GpXy5gJg@mail.gmail.com' \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox