Is there a way to filter

[ghost]

Hi,
I am setting the Apache common log format as suggested and it works great ! thank you very much.

Now I think of limiting logs to only those with status 404 (or another approach to not log those with 200 or 304) if feasible.
Do you offer filtering by inclusion or exclusion ? the second option would be great (all except 200 or 304)

Thanks a lot !

[francislavoie]

See caddyserver/caddy#4690

[ghost]

Ok thanks @francislavoie , I guess this is work in progress or being discussed. so I'm going to wait

[francislavoie]

There's also this plugin which might do what you need https://github.com/leodido/caddy-conditional-logging for the time being

[ghost]

Unfortunately it looks outdated, checking here the link is dead
https://github.com/leodido/caddy-conditional-logging/blob/8534d30877aa34bdc083ef3cf466821fa3ade019/caddyfile.go#L18

[francislavoie]

No, that's correct. Go module paths do not match github URLs.

[ghost]

Ok thanks a lot I'll give it a try

[ghost]

I think of keeping transform-encoder as it looks more stable for me and the Apache common log format is working perfect.
Less retention time and more compression rotations would be fine

[francislavoie]

You can chain them together. It's not either-or.

[djt]

@francislavoie are you able to give an example of chaining in this context? As much as I have tried, I cannot see how it works. I am fairly new to caddy though so I blame it on that.

[francislavoie]

Like this:

log {
	output stdout
	format if "status ~~ `^4`" transform {common_log}
}

if is the https://github.com/leodido/caddy-conditional-logging part followed by a condition string (as per its README), then you pass it an encoder to chain into, i.e. transform with the option {common_log}.

That said, since Caddy v2.6.0 released last week, we have a skip_log directive caddyserver/caddy#4691 which you can use to match requests you don't want to have access logged.