Having a trace id is a valuable help in reading logs as all events from one event are grouped together. However, we don't always want to have tracing enabled as it can cause quite some costs. To get the best of both worlds, this MR tries to generate a gosoline-specific trace id to include in logs.
[X] Automatically generate trace ids for HTTP requests
[x] Test for other inputs (SQS, Kinesis, ...)
[x] Trace IDs are forwarded with messages via SQS, SNS, Kinesis, ...
Having a trace id is a valuable help in reading logs as all events from one event are grouped together. However, we don't always want to have tracing enabled as it can cause quite some costs. To get the best of both worlds, this MR tries to generate a gosoline-specific trace id to include in logs.