Support Customizable Logging Format in Infinity

Feature request

Background
When deploying models with Infinity, I found that the current log output is not very convenient for log collection and post-processing. For example, the logs often lack timestamps, and the default log format may not meet enterprise logging standards. This makes it harder to integrate with centralized logging systems and to perform effective analysis.

Proposal
I would like to propose adding support for customizing the logging format in Infinity, so that users can better control log output to fit their operational requirements.

Specifically, I suggest:

1. Ability to disable the rich log handler

   • Controlled via an environment variable:
     INFINITY_DISABLE_RICH_HANDLER

2. Ability to customize the basic log format

   • Controlled via an environment variable:
     INFINITY_LOG_FORMAT

3. Ability to customize Uvicorn log formats

   • Controlled via the following environment variables:
     • INFINITY_UVICORN_DEFAULT_FORMAT: Format for default logs
     • INFINITY_UVICORN_ACCESS_FORMAT: Format for access logs
     • INFINITY_UVICORN_DATE_FORMAT: Date format for all logs

Motivation

These changes will allow operators to:

• Include timestamps and structured fields for easier parsing
• Align log formats with enterprise-wide logging standards
• Simplify integration with tools like Fluent Bit, Logstash, or OpenTelemetry

Your contribution

If the community agrees with this proposal, I am happy to contribute a PR to implement this feature.

Start by locating the logging setup for the rich handler and basic format, then find the Uvicorn logging configuration. Done means the requested environment variables control rich-handler use, basic and Uvicorn formats, and date formatting without breaking existing logging behavior.