Currently, the purpose of the API is limited to providing success/error on overall transaction aborts. We should be able to distinguish client-side aborts from the actual server aborts. While client aborts may not be indicative of any direct problems with downstream servers, it's the server aborts that can be used as passive health-checks for the downstream origin hosts. Also, this makes troubleshooting the 'transaction aborts' easier because now we are able to eliminate an entire set of either client-side or server-side investigations, due to the ability to distinguish between them.
Currently, the purpose of the API is limited to providing success/error on overall transaction aborts. We should be able to distinguish client-side aborts from the actual server aborts. While client aborts may not be indicative of any direct problems with downstream servers, it's the server aborts that can be used as passive health-checks for the downstream origin hosts. Also, this makes troubleshooting the 'transaction aborts' easier because now we are able to eliminate an entire set of either client-side or server-side investigations, due to the ability to distinguish between them.