David Luna

Hi @isikhi about the CLA you may want to send an email to [email protected] also I want to ask if you checked my last comment on #3630. The sample you...

Hi @isikhi Thanks for giving implementation details for the issue, it is really helpful :) From your example we noticed `express` is required before agent starts. In that specific case...

Hi @piyusharora1989 looking at the logs I see you're using `webpack` to bundle your app. Is that right? If so you may be facing the issues mentioned in here https://www.elastic.co/guide/en/apm/agent/nodejs/current/starting-the-agent.html#start-bundlers...

Found the `host-metrics` Otel package is sending bad measurements for CPU utilization. Filed an issue https://github.com/open-telemetry/opentelemetry-js-contrib/issues/1718

PR on `apm-contrib` repo to add memory metrics which could be reused in other languages https://github.com/elastic/apm-contrib/pull/84

Alignment in process.cpu and system.cpu metrics at semconv level has been suggested https://github.com/open-telemetry/semantic-conventions/issues/563

PR to fix `process.cpu.time` & `process.cpu.utilization` https://github.com/open-telemetry/opentelemetry-js-contrib/pull/1785 There is a [PR to update process semconv](https://github.com/open-telemetry/semantic-conventions/pull/330) which may change the attribute names. The PR above is prepared to receive the necessary...

In `test-vers (16, patch)` https://github.com/elastic/apm-agent-nodejs/actions/runs/4993987868/jobs/8944295339 Same error message in https://github.com/elastic/apm-agent-nodejs/issues/3313#issuecomment-1548249438 ``` # error.log.stacktrace not ok 21 capture-error-string.js did not error --- operator: error at: done (/home/runner/work/apm-agent-nodejs/apm-agent-nodejs/test/stacktraces/stacktraces.test.js:133:11) stack: |- Error: Command...

In `test-vers (8)`. bluebird timeout tests failing when updating non relater dependency `@apollo/server` https://github.com/elastic/apm-agent-nodejs/actions/runs/5238410127/jobs/9457274122?pr=3414 Time elapsed bigger than expected. Could be that the CI was having high load? ``` not...

# test-vers (21.0), test/central-config-enabled.test.js https://github.com/elastic/apm-agent-nodejs/actions/runs/7084490267/job/19278856820?pr=3767#logs ``` running test: node --unhandled-rejections=strict test/central-config-enabled.test.js > test_output/test-central-config-enabled.test.js.tap 2&>1 TAP version 13 # remote config enabled ok 1 this test uses every available central config...