Prepare for v0.10.0 #2474
josedonizetti
started this conversation in
Development
Replies: 2 comments 3 replies
-
Beta Was this translation helpful? Give feedback.
2 replies
-
@josedonizetti for "everything is event" thing - I think we should explain the motivation and changes in detail, but probably not here. I would suggest starting a GH Discussion (under "development"), that explain all this, and then this changelog can mention the changes in high level and link to the discussion for more info. We could also use the discussion to mention this change in the OSS team monthly update, and also as a way to collect feedback about the concept from community. WDYT? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Draft to collaborate on v0.10.0 release announcement
🚀 What's new? 🚀
🌐 Network events
Tracee now supports network events without the need to specify a network interface AND full network packets headers parsing. All data in & out from monitored tasks are captured as events named:
net_packet_ipv4
net_packet_ipv6
net_packet_tcp
net_packet_udp
net_packet_icmp
net_packet_icmpv6
net_packet_dns
net_packet_dns_request
(backward compatibility withdns_request
),net_packet_dns_response
(backward compatibility withdns_response
)For example, to see IP and ICMP packets being sent to Google DNS servers, from the
ping
command, you may trace thenet_packet_ipv4
andnet_packet_icmp
packets, and filter throughnet_packet_ipv4.args.dst=
argument:🧪 Everything is an event
Tracee collector powers (tracee-ebpf) and tracee rule engine (tracee-rules) are now part of a single experience, as one binary.
This allows for the collection of events to run along the rule engine, for example, see all
execve
along with thedropped_binary
rule.🔎 New filtering features
1. Context Filter
Tracee can now filter according to the internal context of a specific event:
2. Syscall filters
Events with a syscall argument now support using named syscalls as inputs.
3. Binary path filter
Tracee can now filter for events coming from a specific binary path:
🐳 Container image in output
When using the containers enrichment feature while tracing container events, the container's image will be added to the output.
Beta Was this translation helpful? Give feedback.
All reactions