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.

首先检查 ExecutionContext 的日志记录入口，以及其 Logger 如何传递给依赖项方法。将当前的 java.util.Logger 方案与所请求的 SLF4J 和 Lombok 支持进行比较。完成该工作需要达成一致的集成设计，并记录未来日志记录支持的范围。

由索引模型根据 Issue 内容生成。