Hassy Veldstra

hi @rakesh-rameshtr 👋 Honeycomb support is only available for HTTP tests at the protocol level currently (ie using the built-in `http` engine). Great feature request though, we'll look into extending...

That's not supported yet @furqanms, but would be a good feature to support. (I edited your post to add code formatting for the YAML block to make it easier to...

hi @magentaqin 👋 Artillery depends on Node.js v14 or higher. I'm guessing you're running an older version of Node which does not support optional chaining. https://github.com/artilleryio/artillery/blob/master/package.json#L7

Supporting older Node.js versions isn't really something we want to do. We try to match current LTS or latest AWS Lambda runtime version, whichever is newer. A smaller release bundle...

hi @MMaximus111 👋 thank you for the bug report. Is your scenario (the part that's not in the screenshot) sending a cookie anywhere? (with `cookie` attribute on a request -...

https://github.com/ptejada/artillery-engine-socketio-v3 is a great solution for this right now We will hopefully merge into Artillery's main source tree soon :)

hi @savvagen 👋 Artillery v2 removed `customStats`. *All* metrics (from Artillery itself and any custom metrics) are stored under `counters`/`summaries`/`rates` field of the stats object now. So for example, this...

thanks for a very detailed issue report @savvagen! that bit of the plugin API has changed between v1.x and v2.x - Artillery v2 is multi-threaded, but function objects cannot be...

@savvagen you need to add a snippet of code to your custom plugin: ``` if (typeof process.env.LOCAL_WORKER_ID === 'undefined') { debug('Not running in a worker, exiting'); return; } ``` as...

Issue reproduced. Thanks for the bug report @Woolfe! We'll prioritize shipping a fix for this.