[lttng-dev] LTTng container awareness
hai.yang at magic-shield.com
Tue May 25 04:13:48 EDT 2021
LTTng had the 2019 plan to decouple tooling for container awareness, how is the progress on that?
As stated in page 18, LTTng is comprised of many components that expect a “monolitic” system. How about the future to containerize the LTTng?
------------------ Original ------------------
From: "Jonathan Rajotte-Julien"<jonathan.rajotte-julien at efficios.com>;
Date: Tue, Jul 16, 2019 10:28 PM
To: "杨海"<hai.yang at magic-shield.com>;
Cc: "lttng-dev"<lttng-dev at lists.lttng.org>;
Subject: Re: [lttng-dev] Pros and Cons of LTTng
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
If you do not find a particular feature in the doc , 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.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lttng-dev