Delgan

Hi @nopnopwei. Now I understand why you need to call `.add()` multiple times. Although I don't recommend it (for performances reason mainly), it's acceptable. You make a good usage of...

You're welcome, glad it worked. :+1: I'm closing the issue then. ;)

Hi @sukhoi47. Are you using any framework like Uvicorn to implement your web app? The issue you're facing often happen because multiple sub-processes are started which results with `logger.add()` being...

Hey @sukhoi47, thanks for the investigations and the reported edge case. I think you can try using a `datetime.time()` object with `tzinfo` set as `UTC` for `rotation`: ```python logger.add(..., rotation=datetime.time(0,...

Sorry for not answering, but I could not investigate your issue without more details. Feel free to re-open a ticket by please providing a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example).

@yodew Thanks for the additional details! :+1: Then you should probably use the [`InterceptHandler`](https://github.com/Delgan/loguru#entirely-compatible-with-standard-logging) to ensure SkyWalking receive logs emitted by Loguru.

Closing this issue as I think it was an issue with `logger` handling around processes.

@mastern2k3 I'm not sure to understand. ```python logger.info("User data: {}", input()) ``` That would work fine and wouldn't not crash regardless of user data containing curly brackets or not.

@mastern2k3 You can use f-strings as long as you do not call the logging method with formatting arguments: ```python logger.info(f"User data: {user_data}") # Good. logger.info(f"User data: {user_data}", data=user_data) # Bad....

Please, re-open the issue if my answer did not solve your issue.