You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is your feature about ?
It would be nice to be able to register callback functions to trigger specific functionalities when signals are received.
Describe what you'd like
the handling of signals is currently handled by the core, to reopen file descriptors in the Logger after a log rotate.
There are some (many) use-cases when it would be interesting to reopen other files/update models and internal memory maps when a signal is sent to a filter:
reload hostlookup maps
reload DGA tensorflow model
reload yara rules
...
This would prevent users from restarting filters when a file is updated.
Additional context
The functionality could take the form of a Core interface defining and using a list of callbacks to call on each signal, with the ability to add callbacks depending on the needs.
The text was updated successfully, but these errors were encountered:
What is your feature about ?
It would be nice to be able to register callback functions to trigger specific functionalities when signals are received.
Describe what you'd like
the handling of signals is currently handled by the core, to reopen file descriptors in the Logger after a log rotate.
There are some (many) use-cases when it would be interesting to reopen other files/update models and internal memory maps when a signal is sent to a filter:
This would prevent users from restarting filters when a file is updated.
Additional context
The functionality could take the form of a Core interface defining and using a list of callbacks to call on each signal, with the ability to add callbacks depending on the needs.
The text was updated successfully, but these errors were encountered: