Project

General

Profile

Actions

Bug #2493

closed

EngineAnalysisRules2 File Output Cannot Be Adjusted

Added by Danny Browning about 6 years ago. Updated about 5 years ago.

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

Description

Putting this as a bug since as rule reloads occur, the file will continue to grow without bounds or limits.

EngineAnalysisRules2 uses a hardcoded rules.json file in the default output directory to output rules analysis information. This path and whether or not analysis is output should be configurable.

Actions #1

Updated by Danny Browning about 6 years ago

Related MR: https://github.com/OISF/suricata/pull/3346

This method seems to still be in development, and per documentation should only be called when running with --engine-analysis, so there might be a different solution needed.

Actions #2

Updated by Andreas Herz almost 6 years ago

  • Assignee set to Danny Browning
  • Target version set to TBD

Do you want to work on that further?

Actions #3

Updated by Jacob Masen-Smith almost 6 years ago

Is there any particular reason EngineAnalysisRules2 is called where it is? EngineAnalysisRules is called in a completely separate location yet with the same arguments, in a way that respects the `engine-analysis` flag.

Actions #4

Updated by Danny Browning almost 6 years ago

I think Jacob's solution is better than mine, although I'm not sure why there is a profiling config section and the command line argument.

Actions #5

Updated by Victor Julien about 5 years ago

  • Status changed from New to Closed
  • Assignee deleted (Danny Browning)
  • Target version deleted (TBD)

I believe this has been fixed.

Actions

Also available in: Atom PDF