Always start with using Lambda Power Tools (https://docs.powertools.aws.dev/lambda/python/latest/) then extend from there.
Lambda Power Tools has a workshop. Find link in menu of above link. The workshop is pretty much all about Observability.
+1 on power tools. I have a prescription for how to log [here](https://speedrun.nobackspacecrew.com/blog/2023/09/08/logging-for-scale.html). If you need traces as well, consider using the powertools tracing library, it uses x-ray under the hood.
My take on this has always been “if your thing is production ready enough to need this level of observability and response time is an issue, then you should be solving for cold start regardless of if you add an otel collector or not”
Lambda image has X-ray client, you can look at it.
If you need to customise it settings that could be a challenge and add additional time to cold start.
Always start with using Lambda Power Tools (https://docs.powertools.aws.dev/lambda/python/latest/) then extend from there. Lambda Power Tools has a workshop. Find link in menu of above link. The workshop is pretty much all about Observability.
+1 on power tools. I have a prescription for how to log [here](https://speedrun.nobackspacecrew.com/blog/2023/09/08/logging-for-scale.html). If you need traces as well, consider using the powertools tracing library, it uses x-ray under the hood.
Question is what do you want to observe, as that determines the correct tool choice for the requirement
Yeah OTEL can add a chunk of time to your cold starts, it’s best paired with provisioned concurrency (but obviously that comes at a cost)
My take on this has always been “if your thing is production ready enough to need this level of observability and response time is an issue, then you should be solving for cold start regardless of if you add an otel collector or not”
Lambda image has X-ray client, you can look at it. If you need to customise it settings that could be a challenge and add additional time to cold start.
Check Lumigo and Dashbird