Support json format as loglevel in config.yaml about coraza-spoa HOT 9 CLOSED

Although I don't see any problem adding a json output to MatchedRules, I do see a problem adding additional configuration to connectors. Logs are already too complicated for users, we have error, audit and debug, now we would add error log configurations
IMHO it's better if each user parses the coraza lot as it is, then he can transform it into json

from coraza-spoa.

I don't quite understand connectors in this context but I assume it apps that use coraza as a library.

Would it be the right place to add a json formatter here based on a config flag? Don't know if this also is considered a connector or is there a better place to put json logging on the application side.

from coraza-spoa.

+1 to custom serializers, -1 to adding log level to the config. As of now you can configure that in the seclang config, supporting log config somewhere else will be problematic and cumbersome as you need to define a priority that users need to be aware of and still that does not clarify anything.

from coraza-spoa.

+1 to custom serializers, -1 to adding log level to the config. As of now you can configure that in the seclang config, supporting log config somewhere else will be problematic and cumbersome as you need to define a priority that users need to be aware of and still that does not clarify anything.

Can you give any example configurating this via seclang? Is it something we would have to define here?

from coraza-spoa.

from coraza-spoa.

check https://coraza.io/docs/seclang/directives/#secdebuglog
…

I don't really get it. How can we use this? Is this a replacement for the logging at https://github.com/corazawaf/coraza-spoa/blob/main/config.yaml.default#L29-L32?

from coraza-spoa.

I don't quite understand connectors in this context but I assume it apps that use coraza as a library.

Yup, you're right.

Is this a replacement for the logging at https://github.com/corazawaf/coraza-spoa/blob/main/config.yaml.default#L29-L32?

Of course, no :)

Should be something like that on coraza's side for Debug and Error logs, I think.

@devasmith, while your hack works for Coraza's error log, I would like to attract attention to Connector's logs as well as other libraries.

from coraza-spoa.

I just noticed this change: https://github.com/corazawaf/coraza-spoa/pull/90/files#diff-d0effb22dac9e11bf39bf7ede9c5a9802da85a46a39fe39fe2c81fec1a3ddda6R22-R23

This is what I was after and it seems to be implemented in that draft.

from coraza-spoa.

Oh, OK. I guess I won't say anything about #90. Wish you luck 🤝

from coraza-spoa.