Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

detect-engine: make output configurable (bug #2493) #3346

Closed

Conversation

dbcfd
Copy link

@dbcfd dbcfd commented Apr 19, 2018

Detect engine has a new rules analysis method that is outputting analysis as json to a file. This
output is not currently configurable, so checking existing config settings to see if rules analysis
should be output.

Make sure these boxes are signed before submitting your Pull Request -- thank you.

Link to redmine ticket:

https://redmine.openinfosecfoundation.org/issues/2493https://redmine.openinfosecfoundation.org/issues/2493

Describe changes:

  • Use config to determine if rules analysis should be output

PRScript output (if applicable):

Detect engine has a new rules analysis method that is outputting analysis as json to a file. This
output is not currently configurable, so checking existing config settings to see if rules analysis
should be output.

https://redmine.openinfosecfoundation.org/issues/2493
@dbcfd dbcfd requested a review from a team as a code owner April 19, 2018 15:13
@victorjulien
Copy link
Member

QA fail

@dbcfd dbcfd deleted the rules-engine-output-configurable-bug2493 branch October 6, 2019 14:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants