As a hub operator and technical expert responsible for troubleshooting failed transactions and auditing, I want to access audit logs containing comprehensive information in discovery phase about transactions so that I can effectively perform troubleshooting and auditing tasks.
Acceptance Criteria:
Audit logs should cover transactions occurring within the hub and all activities performed via the admin portal.
Logs should include related IDs such as transaction ID and activity action taker ID etc.
logs should be included the exact time that transaction/activities happened in UTC.
Information about the related service, Bounded Context (BC), and application involved should be provided.
For failed transactions, a detailed error description explaining why the transaction failed should be included. The error description should not be generic and should facilitate effective troubleshooting.
The logs should indicate the state in which the transaction failed, such as the state where party information is returned or when liquidity is insufficient.
Error descriptions should cover all scenarios outlined in the Mojaloop guidelines. Mojaloop error codes
User Story:
As a hub operator and technical expert responsible for troubleshooting failed transactions and auditing, I want to access audit logs containing comprehensive information in discovery phase about transactions so that I can effectively perform troubleshooting and auditing tasks.
Acceptance Criteria: