Hassy Veldstra

Thanks @Cmiroslaf! It's very difficult to see where the change is exactly though because the entire file seems to have been reformatted. Would you mind updating the PR keeping the...

You're right @gboysko, there's nothing like it in Artillery yet, but it's definitely something worth adding! What is your exact use case? One way to do it would be to...

Cool, this is definitely a needed feature (not just for Socket.io either, but also for WebSockets and any other async protocol we want to support like MQTT or XMPP). As...

@gboysko yep, in the HTTP engine handler functions can do one of two things: 1. Emit an `error` event which will log the error (in the shell output / JSON...

@gboysko any luck? (if you've had the time) feel free to open a WIP PR, I'm happy to help out!

@gboysko yes, #171 is certainly something very useful!

For when we're implementing this feature - we now have the means to attach a handler to any incoming message in Socket.io now: https://github.com/shoreditch-ops/artillery-core/pull/192/commits/ed21d66a87f736e49ec7543a1f571fe744a5936a#diff-4c8bbeda468bf6bfdd048bd21ee2d037R248

Thank you for the bug report @vicks07! Does this happen sporadically or every time you try to run a test? If possible, when it happens again, could you take a...

hi @meetveera 👋 that's odd, Artillery's Datadog integration sends `vusers.created` metric as a counter to Datadog, so you'd expect the counts to match as long as you're summing the metric...

I'm not sure why that's happening, all of those metrics should be reported in the exact same way by Artillery's Datadog integration. 🤔