Fiber Logger middleware output destination and format customization

The Fiber framework provides a built-in Logger middleware to capture request metadata such as method, path, status code, and latency. While the Config struct allows for basic customization of the output format, there is a need to determine the most efficient way to redirect these logs to a structured external logging system without introducing significant latency in a high-traffic environment.

Because Fiber utilizes a fasthttp-based architecture, the handling of request contexts differs from the standard net/http library. This raises questions regarding the optimal implementation of custom log writers that must maintain thread safety and performance.

• What are the supported methods for overriding the default console output in the Logger middleware to use a custom io.Writer?
• How can the log format be modified to output structured JSON instead of the default string format?