afterResponse not triggered in case of connection error

[gerasimos]

Hello,

I've notice that afterResponse is not triggered in case of connection errors (timeouts, invalid host etc) such as ECONNREFUSED (on the other hand, such cases are reported in the artillery output).

[hassy]

If a connection is refused there's no response to call the function on. :)

[gerasimos]

OK, I understand this. In any case, is there any chance to have this in a next release? Or, how else can I (custom) log such cases?

There is onError which is scenario-based and haven't figure out how to use it in the yaml file. Can something similar be applied per request?

Thank you,
Gerasimos

[hassy]

You can use a scenario-level onError hook with the following signature:

function myOnErrorHandler(err, requestParams, context, events, callback) {
  // ...
  return callback();
}

[gerasimos]

Thank you, that works for my case.

[trajano]

Where is this documented?

[trajano]

For those who got here, I posted a solution to this in https://stackoverflow.com/questions/71273683/in-artillery-how-do-i-log-etimedout/71332728#71332728