Thanks Affan. I'm impressed by these two projects, especifily cilium. I will 
spend more time to study it.
As there have many tools in bcc collection, so perhaps conmon also can move to 
<https://github.com/iovisor/bcc/tree/master/tools>, then may lead more people 
to write container monitoring scripts by python+bcc, just my 2 cents. :)

------------------------------------------------------------------发件人:Affan 
Ahmed Syed <[email protected]>发送时间:2016年11月28日(星期一) 18:37收件人:张维(贤维) 
<[email protected]>抄 送:developer <[email protected]>主 题:Re: 
[iovisor-dev] Container Oriented Support in Bcc
Hello,Yes, there is several activity in this regards, I was involved in one 
which was demoed recently at Openstack Summit [1] for security monitoring of 
containers. 
The Cilium project [2] is another place focusing specifically on container 
networking. 
Affan

[1] https://github.com/akhayam/conmon
[2] 
https://opensource.googleblog.com/2016/11/cilium-networking-and-security.html
On Mon, Nov 28, 2016 at 11:08 AM, 张维(贤维) via iovisor-dev 
<[email protected]> wrote:
Hi guys,
I'm a new-bie to IO visor project, so excited to know the effort like this. 
https://github.com/iovisor/bcc(I've been working on Linux dynamic tracing for 
many years, so quite familiar with Linux kernel and ebpf.)
As container is been popular deployed in modern infrastructures, I would like 
to know if there have any plan or ideas to support container oriented 
tracing/debugging in IO-Visor bcc project. For example:1. Trace the syscalls of 
all processes in a container.(currently we have too add CAP_PTRACE when we 
start conatiner, then use strace in container)2. Trace the disk/volume activity 
in a container.3. Trace the network packet activity in a container.
There requirements is quite simple if target is a normal Linux process, as 
infrastrcture changes, container is the new modern type process nowadays IMO, 
container oritented support would be a general demands for many Linux tools.
Best Regards.

_______________________________________________

iovisor-dev mailing list

[email protected]

https://lists.iovisor.org/mailman/listinfo/iovisor-dev



_______________________________________________
iovisor-dev mailing list
[email protected]
https://lists.iovisor.org/mailman/listinfo/iovisor-dev

Reply via email to