Skip to content

Option to not rewrite the logging configuration #420

@carlosemart

Description

@carlosemart

Is your feature request related to a problem? Please describe.
We are integrating FastMcp into a larger python process that requires a custom logging handler and when initialising the FastMCP server (in our case in sse mode) we see that the logging library configuration changes with a custom configuration of the server itself.

Describe the solution you'd like
Define a configuration parameter that disables the logging configuration performed by the server.

Describe alternatives you've considered
Reviewing the configuration parameters I have seen the existence of the parameter log_level (

log_level: Literal["DEBUG", "INFO", "WARNING", "ERROR", "CRITICAL"] = "INFO"
) and perhaps if this parameter allowed the value None this could prevent the reconfiguration from being carried out.

Additional context
As far as I have been able to identify, there are two points where this configuration is being made and which should be modified:

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1Significant bug affecting many users, highly requested featureenhancementRequest for a new feature that's not currently supportedneeds decisionIssue is actionable, needs maintainer decision on whether to implement

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions