Releases: bookingcom/bpfink
Releases · bookingcom/bpfink
0.6.46
- Update log/event metrics to use Counter instead of Meter to reduce no. of events sent to graphite storage.
- Remove per-host metrics, cover them along with per-role
0.6.45
Collection of the following metrics -
- Events caught on the bpf side
- Logs produced
0.6.44
Metrics for logs and events caught
0.6.43: Fix the "Consumer not found error" (#31)
1. Add similar inode/dev match logic (see ) to the rest of the probes 2. remove bpf_map_update_elem call from trace_done_path_create probe. This call creates the situation when we have a rule in ebpf, but don't have a rule on the agent side. In combination with 1 it leads to "Consumer not found error" Exact scenario: create subdirectory in directory which has the same inode number as monitored directory but different device id, due to bug 1 we will treat this event as relevant and due to bug 2 we add that inode to our rule map and therefore will monitor any changes for the unrelevant subdirectory. Agent on the contrary doesn't know anything about that directory (because it belongs to diffrent fs) and will spam with "Consumer not found" message on every such event
0.6.42
Add consumer to parser sudoers files.
0.6.37
Exclude files from generic file monitoring specifically
0.6.36
Ability to exclude irrelevant files from monitoring.