Actions
Bug #7236
closed
JI
JI
plugins: custom transaction loggers cannot be registered by a plugin
Bug #7236:
plugins: custom transaction loggers cannot be registered by a plugin
Affected Versions:
Effort:
Difficulty:
Label:
Description
A plugin that might want to register custom transaction loggers cannot do so as the initialization point of the plugin occurs before the app-layer portion of the configuration file has been processed. This results in the registration function failing to register the logger as the protocol is not enabled.
Possible solutions:
- Move the call to the plugin .Init function later (if this won't break anything)
- Move plugin loading later (if this won't break anything)
- Provide a new callback that happens sometime after app-layer has been processed, but research what makes sense here.
JI Updated by Jason Ish over 1 year ago
- Priority changed from Normal to High
PA Updated by Philippe Antoine about 1 year ago
Is this now possible after merge of https://github.com/OISF/suricata/pull/12383 ?
PA Updated by Philippe Antoine about 1 year ago
- Related to Task #4101: tracking: plugins added
PA Updated by Philippe Antoine about 1 year ago
- Related to Task #7151: plugins: add template app-layer plugin added
VJ Updated by Victor Julien about 1 year ago
- Target version changed from 8.0.0-beta1 to 8.0.0-rc1
VJ Updated by Victor Julien 10 months ago
- Status changed from New to Assigned
JI Updated by Jason Ish 10 months ago
- Status changed from Assigned to In Review
Pull request: https://github.com/OISF/suricata/pull/13393
JI Updated by Jason Ish 8 months ago
- Related to Documentation #7840: userguide: document transaction loggers can be registered from a plugin added
Actions