Serverless applications help speed up development and independence and allow the execution which triggers events, but when these function do not work as expected, how do we verify that events are activating the right functions? With serverless applications, the root cause analysis becomes more complicated, because services are small and their functionality is very precise. While trying to track down the fault source, neither the services involved nor any of the integration points actually exist, and when there is more than one function which takes part in the operation, the investigation becomes very difficult.
That is where the logs plays a vital role, but there are some unique considerations which need to be taken into account when logging into a serverless architecture. And it is normal for several functions to fail and not to deliver the requested functionality, or for the logs contain a unified identifier for the transaction, so when function logs are analysed...