Thomas Watson

Results 112 comments of Thomas Watson

Maybe it's related to the number of CPU cores available? You might also be able to reproduce it on macOS if you force it to use the "generic" path

Are you trying to use the agent in a browser? If so, that's not supported. You might want to take a look at the [JavaScript Real User Monitoring agent](https://github.com/elastic/apm-agent-rum-js) instead....

@vigneshshanmugam The Node.js agent use dynamic require-statements in all the 3 locations pointed out by the warnings. The [first](https://github.com/elastic/apm-agent-nodejs/blob/50cc8f32f9ff09a8bc3f79f46b391d85174552ca/lib/agent.js#L152) [two](https://github.com/elastic/apm-agent-nodejs/blob/50cc8f32f9ff09a8bc3f79f46b391d85174552ca/lib/config.js#L25) is not strictly needed and can just be ignored (you...

Not sure what's best though: Showing the warning to the user so they know not to run it in the browser, or trick Webpack by obfuscating the code so it...

FYI: The API for getting the `traceparent` is now public and has just landed in v2.9.0: 3 new getters have been added from which you can get the `traceparent` string:...

The new docs are building as we speak... they take about 30 minutes to 1 hour to get online

You can see it in the docs from the `master` branch: https://www.elastic.co/guide/en/apm/agent/nodejs/master/agent-api.html#apm-current-traceparent

haha yep 😇 ... and yes, they all return the same type of string - the same we automatically add to outgoing http headers

That was released 10 hours ago, so it should be fine 🤔 If you look on npm it's there: https://www.npmjs.com/package/elastic-apm-http-client

I have no experience with yarn, but maybe it has an internal cache that somehow needs to be cleared?