The current logging is not user friendly. Any plan for supporting Slf4j in future?

In my understanding the only current logging option is to get a Logger instance from ExecutionContext. we have to pass this logger instance onto any dependency method incase we want to add more loggings in dependent methods too. Also java.util.Logger is an older way to manage logs in java application which is not user friendly.
Here is a link - (https://stackoverflow.com/questions/11359187/why-not-use-java-util-logging)

slf4j(https://www.slf4j.org/) is a nice framework to manage logs in a user friendly way.Its also supports a better and user friendly string substitution for logs (https://www.slf4j.org/api/org/slf4j/helpers/MessageFormatter.html)

Is there any plan for supporting slf4j in future?

Ideally if Azure java functions can support lombook(@Slf4j) as first class citizen , we can annotate function and other classes with @Slf4j and rest of the logging is really easy to follow, rather than deriving Logger from ExecutionContext and passing it everywhere.

Let me know your thoughts.

Commencez par examiner le point d’entrée de journalisation de ExecutionContext et la manière dont son Logger est transmis aux méthodes des dépendances. Comparez l’approche actuelle fondée sur java.util.Logger avec la prise en charge demandée de SLF4J et Lombok. La tâche sera considérée comme terminée lorsqu’une conception d’intégration validée et un périmètre documenté pour la future prise en charge de la journalisation seront disponibles.

Rédigé par le modèle d'indexation à partir du texte de l'issue.