Why You Should Use context.logger in Lambda Durable Functions

This article is a machine translation of the contents of the following URL, which I wrote in Japanese: Lambda Durable Functions のロギングには context.logger を使用しよう #Python - Qiita はじめに こんにちは、ほうき星 @H0ukiStar です。 皆さんは Lambda Durable Functions を使っていますでしょうか？ Lambda Durable Functions は Lambda 関数単体で Step Functions のようなマル... qiita.com Introduction Hi, I'm @H0ukiStar. Have you tried using Lambda Durable Functions? Lambda Durable Functions is a feature that allows you to implement multi-step workflows—similar to Step Functions—using only a single Lambda function. When implementing logging in Lambda Durable Functions, it is recommended to use context.logger and step_context.logger. But why is that? In this article, I’ll explain the reason based on actual behavior and implementation details. Logging with the Standard Method First, in a typical Lambda function (Python), logging is usually done using the built-in logging module, like this: import logging logger: logging.Logger = logging.getLogger() logge