-
Notifications
You must be signed in to change notification settings - Fork 71
Add log format definition for perflogjson #128
Comments
I don't think this log format makes any sense for us. Probably this is a leftover from a different installation from the vshn team. So I'm closing this one as won't fix. |
I suspect it's been a VSHN->JSON version of the perflog I'm advocating in my ModSec->Apache tutorial here: https://www.netnea.com/cms/apache-tutorial-6_embedding-modsecurity/#step_5_creating_the_base_configuration This is hardly used in production and nothing wrong with removing it. |
Thanks for the hint! |
The one thing you may want to make the Apache default is the
Explained and spiced up with aliases to extract the individual columns in this tutorial: https://www.netnea.com/cms/apache-tutorial-5_extending-access-log/#step_4_configuring_the_new,_extended_log_format The ModSec variables are defined here: https://www.netnea.com/cms/apache-tutorial-6_embedding-modsecurity/#step_5_creating_the_base_configuration |
Thanks. I've opened an issue: coreruleset/modsecurity-crs-docker#97. |
We currently use a custom log format named
perlogjson
for the performance log of Apache. This log format doesn't exist though. It was introduced in cfe220b but without a format definition.The text was updated successfully, but these errors were encountered: