Better troubleshooting support

JuroOravec commented 3 months ago

Description

I had hard time trying to get to the root of https://github.com/oxyno-zeta/s3-proxy/issues/441. Along the way, I used the s3-proxy's webhook feature to send the request events to an http-echo service.

I think it would be great if we could make it easier for other to debug, so they don't have to go through the same as I did.

Suggestions

Extra logging info:
1. The requested path
2. The path used for regex comparison (bucket prefix + requested path)
3. If any of the targets matched or not, and which one if so
4. The re-written path - AKA the final path that will be sent to S3
Add docs section on troubleshooting, describing how to set the log level to debug and what kind of info is available.

github-actions[bot] commented 2 months ago

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 10 days

JuroOravec commented 2 months ago

Not stale

oxyno-zeta / s3-proxy