George Mihai

I believe the library restructures the element you initialize it on, causing previous references to any child elements to be lost. I've been able to work around this issue by...

Hello again, After further investigation and playing around with lambda timeouts and agent timeouts, I've reached a very interesting issue: The APM agent stopped having these problems, while some aws-sqs...

> Another question for you. You checked this option above and showed those config options. Are you actually explicitly calling `apm.start(...)` in your Lambda code? The [expected way to configure...

Hello, I did proceed as you instructed, I switched to using the APM agent layer, removed all .start() calls and removed the .lambda() wrapper. The APM issues stopped, however I...

Hello again! We have identified the issue as being related to an SQS payload exceeding the allowed limits of 256kb. The initial error I reported was likely caused by a...

@trentm I did in fact validate this, and after disabling APM completely, the increase in memory remained the same. It seems that there was a very large object being loaded,...

Hello, Reopening this as we're still experiencing some issues with this error. Right now I am on elastic-apm-extension v1.3 and elastic-apm-node v3.43.0, and after I deployed a high throughput lambda...

Hello, Looks like the timeout is simply the lambda timeout, which kills the execution after 30 seconds. The `ELASTIC_APM_API_REQUEST_TIME` value is not set, so it's expected to be the 10s...

+1 on this. This purifier doesn't appear to have the service for changing fan levels. Instead, the fan level can be manually set on the Favorite preset. The solution would...