From: "杨海 via lttng-dev" <lttng-dev@lists.lttng.org>
To: "Jonathan Rajotte-Julien" <jonathan.rajotte-julien@efficios.com>
Cc: lttng-dev <lttng-dev@lists.lttng.org>
Subject: [lttng-dev] LTTng container awareness
Date: Tue, 25 May 2021 16:13:48 +0800 [thread overview]
Message-ID: <tencent_02D5BD1E0DB6EEBD7DC3A97D@qq.com> (raw)
In-Reply-To: <20190716142832.GA20789@joraj-alpa>
[-- Attachment #1.1: Type: text/plain, Size: 1909 bytes --]
Hi
LTTng had the 2019 plan to decouple tooling for container awareness, how is the progress on that?
https://archive.fosdem.org/2019/schedule/event/containers_lttng/
As stated in page 18, LTTng is comprised of many components that expect a “monolitic” system. How about the future to containerize the LTTng?
Regards
Hai
------------------ Original ------------------
From: "Jonathan Rajotte-Julien"<jonathan.rajotte-julien@efficios.com>;
Date: Tue, Jul 16, 2019 10:28 PM
To: "杨海"<hai.yang@magic-shield.com>;
Cc: "lttng-dev"<lttng-dev@lists.lttng.org>;
Subject: Re: [lttng-dev] Pros and Cons of LTTng
Hi Hai,
On Tue, Jul 16, 2019 at 10:19:38AM +0800, 杨海 wrote:
> Obviously LTTng has much lower overhead compared to auditd, when we turn on
> all system calls and use the same load. Is it true for both user space and
> kernel space?
lttng-ust (userspace tracer) mostly use the same concept as the kerneltracer
(per-cpu ring buffers, binary output/CTF, delayed consumption of events, etc.).
There is some penalty for doing things in userspace since we need some
information from the kernel for each tracepoint hit (e.g the current cpu
number). But again most of these hot paths are quite optimized.
In any case I encourage you to try it out on your workload and lttng fit your
needs.
If you do not find a particular feature in the doc [1], do not hesitate to contact
this mailing list for more information.
>So far I haven't seen any report compare LTTng and auditd,
> anyone knows?
I do not remember any conversation on this topic. After reading a bit on auditd,
lttng might be a good replacement depending on your constraints and needs.
[1] https://lttng.org/docs/v2.10/
Cheers
--
Jonathan Rajotte-Julien
EfficiOS
[-- Attachment #1.2: Type: text/html, Size: 3057 bytes --]
[-- Attachment #2: Type: text/plain, Size: 156 bytes --]
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
prev parent reply other threads:[~2021-05-25 8:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_7588A64434D8A77544C70CAA@qq.com>
2019-07-16 14:28 ` Pros and Cons of LTTng Jonathan Rajotte-Julien
[not found] ` <20190716142832.GA20789@joraj-alpa>
2021-05-25 8:13 ` 杨海 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=tencent_02D5BD1E0DB6EEBD7DC3A97D@qq.com \
--to=lttng-dev@lists.lttng.org \
--cc=hai.yang@magic-shield.com \
--cc=jonathan.rajotte-julien@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;
as well as URLs for NNTP newsgroup(s).