Best practice for enabling Traefik access logs and mapping them to host for Fail2Ban integration(or other recommended way)

Hi everyone,

I'm currently running Traefik managed by EasyPanel and I’m trying to integrate it with Fail2Ban to add an extra layer of protection against basic abuse patterns (like repeated failed login attempts, scanners, etc.).

From what I understand, the correct approach is to enable Traefik access logs (preferably in JSON format), expose those logs to the host filesystem, and then configure Fail2Ban to monitor them. However, since Traefik is managed by EasyPanel, I want to make sure I’m doing this in a way that doesn’t interfere with the platform’s internal configuration (routing, TLS, providers, etc.).

Here are the main challenges I’m facing:

What is the recommended way to enable access logs via EasyPanel without overriding or breaking the default Traefik configuration? Is there an official or safe way to define a custom accessLog block (e.g., JSON format, filePath) through EasyPanel? Where should the log file be written so that it persists and is accessible from the host? How can we properly map or expose that log path (volume) to the host filesystem? Are there any existing examples or recommended setups for integrating Fail2Ban with Traefik in an EasyPanel environment?

My goal is to follow best practices and avoid fragile or unsupported workarounds, especially since incorrect configuration could break networking or SSL.

If there is any official documentation, recommended pattern, or even a reference setup, I would really appreciate it.

Thanks in advance for your help and for the great work on EasyPanel.