Capture and forward correlation IDs through different Lambda event sources

Server­less archi­tec­tures are microser­vices by default, you need cor­re­la­tion IDs to help debug issues that spans across mul­ti­ple func­tions, and pos­si­bly dif­fer­ent event source types — asyn­chro­nous, syn­chro­nous and streams. This is the last of a 3-part mini series on man­ag­ing your AWS Lamb­da logs. If you haven’t read part 1 yet, please give it a read now. …

Cap­ture and for­ward cor­re­la­tion IDs through dif­fer­ent Lamb­da event sourcesRead More »

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.