libs
libs copied to clipboard
Umbrella: Adding support for new field types in plugins
Motivation
Currently, the plugin API only supports uint64 and charbuf field types. However, could be a good idea to add support for additional types to align with the libsinsp library.
Feature
The following types need to be added:
- [ ]
none - [ ]
int8 - [ ]
int16 - [ ]
int32 - [ ]
int64 - [ ]
uint8 - [ ]
uint16 - [ ]
uint32 - [x]
uint64 - [x]
bytebuf - [ ]
errno - [ ]
sockaddr - [ ]
socktuple - [ ]
fd - [ ]
pid - [ ]
fdlist - [ ]
fspath - [ ]
syscallid - [ ]
sigtype - [x]
reltime - [x]
abstime - [ ]
port - [ ]
l4proto - [ ]
sockfamily - [x]
bool - [ ]
ipv4addr - [ ]
dyn - [ ]
flags8 - [ ]
flags16 - [ ]
flags32 - [ ]
uid - [ ]
gid - [ ]
double - [ ]
sigset - [ ]
charbufarray - [ ]
pt_charbuf_pair_array - [ ]
ipv4addr - [ ]
ipv4net - [ ]
ipv6addr - [ ]
ipv6net - [x]
ipaddr - [x]
ipnet - [ ]
mode - [ ]
fsrelpath - [ ]
enumflags8 - [ ]
enumflags16 - [ ]
enumflags32 - [ ]
max
Probably not all these types are useful. Additionally adding all these types, maybe, could result in performance penalties.
Tasks
- [ ] Add support for new filtercheck types.
- [ ] Test the new filtercheck types.
- [ ] Ensure compatibility with
driver/ppm_events_public.h. - [ ] Update documentation to reflect the changes.
Additional context
These types should be compatible with the types declared in the driver/ppm_events_public.h in the libs repository.
This issue will be used only for tracking.
I will add milestone 0.11.0 just to track it :) Feel free to change it /milestone 0.11.0
Hey @therealbobo , I don't think we need all of them :) Also because perhaps the types that sinsp supports are a bit too many :)
I think it makes sense to start from a minimal list and add more when necessary
You are right! I already started to work on it and implemented some basic types! 😄
/assign
/milestone 0.12.0
/milestone 0.13.0 assuming this is a long-term task
@leogr: The provided milestone is not valid for this repository. Milestones in this repository: [0.11.0, 0.12.0, 0.13.0, 5.0.0+driver, next-driver]
Use /milestone clear to clear the milestone.
In response to this:
/milestone 0.13.0 assuming this is a long-term task
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten
/remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community. /close
@poiana: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with
/reopen.Mark the issue as fresh with
/remove-lifecycle rotten.Provide feedback via https://github.com/falcosecurity/community. /close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
/remove-lifecycle rotten
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale
/remove-lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale
/remove-lifecycle stale