You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Are there any plans to implement JSON parsing support in order to support server software that emit structured logs?
Description
I was trying to write some configuration files so that Fail2ban would work with the Caddy webserver (which emits JSON access logs), but realized matching stuff within JSON using regex might be a bad idea. Off the top of my head the JSON structure might change around causing the filter to break, or match incorrect host addresses, etc.
Considered alternatives
Use something like jq to pre-process and extract needed data (possibly issue #2992?)
I haven't found a general issue/RFE for JSON parsing via searching, but please let me know if there is one and this is a duplicate and I will close it.
The text was updated successfully, but these errors were encountered:
I'd be really happy to have this as a native functionality. Right now, our only option is to rely on hacks where Caddylogs are RegEx'd in order to be parsable by fail2ban.
Feature request type
Are there any plans to implement JSON parsing support in order to support server software that emit structured logs?
Description
I was trying to write some configuration files so that Fail2ban would work with the Caddy webserver (which emits JSON access logs), but realized matching stuff within JSON using regex might be a bad idea. Off the top of my head the JSON structure might change around causing the filter to break, or match incorrect host addresses, etc.
Considered alternatives
Use something like
jq
to pre-process and extract needed data (possibly issue #2992?)Any additional information
Issues (for specific server software):
I haven't found a general issue/RFE for JSON parsing via searching, but please let me know if there is one and this is a duplicate and I will close it.
The text was updated successfully, but these errors were encountered: