A development team is refining their serverless application's logging approach to enable better insight during debug sessions. They need the capability to effortlessly filter and search through log entries for specific execution contexts like the runtime version and unique request identifiers. Which logging strategy should the team employ to ensure their log data is conducive to rapid and effective troubleshooting?
Focus on capturing only exception stack traces in the log files, considering that this information suffices for pinpointing issues.
Use a rudimentary logging mechanism that captures standard output streams without specific structure to save on storage space.
Depend solely on a distributed tracing service to monitor the application, presuming it alleviates the need for detailed logs.
Adopt structured logging with a consistent format like JSON that supports key-value pairs for all pertinent information, enhancing the interpretability and searchability of the logs.