wpessers

Interesting, will consider this approach as well. Let me find out if we can work with this, and if yes if we can make the suppression of internal instrumentation more...

I know I'm late on the response here but @nic-littlepay I haven't had time to deep-dive into your problem as I'm a little bit more experienced with how this works...

I lost sight of this, but related to #1826 Tomorrow I have some time to examine layer size / cold start impact, so will get to it!

I'm not entirely sure this change is really adding something new. There is already a `faas.instance` resource attribute which I believe should be handled by the aws resource detector (in...

Upon closer inspection, it looks like this may only be supported in node.js and java

So in my opinion, this feature is already solved in a different way. I believe otel already supports aws lambda resource detection for most languages, which should include the `faas.instance`....

> This also makes me think that we should at some point add an integration test suite that runs in AWS against all supported lambda runtimes - at least before...

Upgrading lerna will indeed fix the vulnerabilities. But I'm wondering why dependabot did not pick this up, as I've seen it propose dependency upgrades for versions that use caret before....

whoops, I was typing out that review but in the meantime you've already responded to Serkan's comment I see. The thing about the versioning-strategy I linked above may be worth...

@herin049 I see your solution captures all the logs by default. Does it also fix the issue, so can you exclude the extension logs and only get function and platform...