Skip to content

fix logging issues #1997

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

Closed
wants to merge 4 commits into from
Closed

fix logging issues #1997

wants to merge 4 commits into from

Conversation

arminabf
Copy link

@arminabf arminabf commented Jan 11, 2019

mod_security does not allow per-module log level configuration nor to log module information into error_log. For example, following does not work

LogLevel security2:info
ErrorLogFormat "{"\"module\":\"%m\", \"level\":\"%l\", \"message\":\"%M\"}"

In the later example no module information is logged. Commit 1f4b951 fixes these issues.

In addition, custom log formats are not applied for messages being logged at startup. Commit b9e8317 fixes some (even though not all) log messages where only the default log format is applied.

Please note that there are more log messages having that problem but that would need far-reaching changes. For example in the function msc_status_engine_call() that is also used by standalone/api.c where no server_rec is available.

@victorhora victorhora added enhancement 2.x Related to ModSecurity version 2.x pr available labels Feb 2, 2019
@victorhora victorhora added this to the v2.9.4 milestone Feb 2, 2019
@marcstern
Copy link

Replaced by #3166

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2.x Related to ModSecurity version 2.x enhancement pr available
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants