The javascript runners honour the x-request-id header by propagating its value to process.env.__OW_TRANSACTION_ID. this allows to easily track a set of actions that are invoked within one transaction.
Unfortunately, the process.env.__OW_TRANSACTION_ID is not sent along when using the openwhisk js client. all it would need is to set the x-request-id header accordingly when invoking an action.
The javascript runners honour the
x-request-id
header by propagating its value toprocess.env.__OW_TRANSACTION_ID
. this allows to easily track a set of actions that are invoked within one transaction.Unfortunately, the
process.env.__OW_TRANSACTION_ID
is not sent along when using the openwhisk js client. all it would need is to set thex-request-id
header accordingly when invoking an action.also see my experiments here: https://gist.github.com/tripodsan/9e0f04e1a5572c0ead3d53d93fab0a2f