Configure captureHttps behaviour

[chrismatheson]

currently the default captureHttps behaviour treats 404 responses as errors. In my particular use case 404 is an acceptable response so these errors are essentially false positives.

it there a way to configure the behaviour in this case? or possibly to opt out of generic X-ray behaviour for the particular call and instrument manually?

[wangzlei]

In xray http instrument we hardcode 404 status code as error as a generic requirement, it is not configurable.
as a workaround, you can maintain your custom logic by overriding https://github.com/aws/aws-xray-sdk-node/blob/master/packages/core/lib/utils.js#L18