If you are referring to Ray clearing or overriding your application’s logging configuration, this issue was addressed in Ray 2.6.2 and confirmed to be fixed in later versions. Upgrading Ray to the latest version should resolve the problem, as users have reported that custom logging configurations persist as expected after upgrading. Downgrading to 2.6.2 is not necessary; upgrading is recommended instead. See the discussion for confirmation and upgrade instructions.
Would you like more detail on how to upgrade or test your logging configuration?
Sources:
Hint: Mention @RunLLM in the post for followups.