Project

General

Profile

Actions

Bug #6408

closed
JL JL

Output plugins receive identifier, but not thread identifier

Bug #6408: Output plugins receive identifier, but not thread identifier

Added by Jeff Lucovsky over 2 years ago. Updated 11 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Affected Versions:
Effort:
Difficulty:
Label:

Description

Currently, output plugins receive a "thread_id" during per-thread initialization. The thread id is actually a slot number for an internal data structure and thus, not useful for correlating to the Suricata thread.

Instead, the per-thread init function should receive a correlating value to the Suricata threads. The semantic change should be unnoticed by output plugins as the id will continue to be unique for different Suricata threads.

JL Updated by Jeff Lucovsky over 2 years ago Actions #1

  • Description updated (diff)

JL Updated by Jeff Lucovsky over 2 years ago Actions #2

  • Status changed from Assigned to In Review

JI Updated by Jason Ish about 2 years ago Actions #3

  • Target version changed from TBD to 8.0.0-beta1

JL Updated by Jeff Lucovsky about 2 years ago Actions #4

  • Status changed from In Review to Closed

VJ Updated by Victor Julien over 1 year ago Actions #5

JI Updated by Jason Ish 11 months ago Actions #6

JI Updated by Jason Ish 11 months ago Actions #7

I dissociated this from the plugin story, as this isn't really about plugins, but the internal logging registration APIs. Which may be used by plugins, but are also used internally.

Actions

Also available in: PDF Atom