We capture each publish transaction details in a custom db which has details of the transaction being published like: item being published, who published it, which version of the item is published, when it was published, publication target etc.
We have created a GUI extension to enable this information for the user on item selection.
We have a fully scaled up architecture where we have separate CM, Publisher and deployer servers.
Need: I am looking to augment this information with the transaction state as well for each transaction
Question: Is there any option available at the transport layer on the publisher to capture the transaction state like whether the transaction was successful or not? The publisher definitely knows the state of the transaction since I can see that in tcm publisher logs, but not sure how to intercept the information and capture it at the transport layer.
I know of other options of capturing the state at the deployer extension post transaction commit or in the event system but I am looking to capture the same at the transport/publisher layer since I am capturing rest of the details at the transport layer. Please let me know