This pull request fixes mulesoft-consulting/json-logger#20 by changing the key of the timer from eventId to correlationId so that it doesn't change between calls to the JSON logger for an API call.
I left the two debug level logging statements that I used to troubleshoot as they may be helpful if a similar situation arises in the future.
This pull request fixes mulesoft-consulting/json-logger#20 by changing the key of the timer from eventId to correlationId so that it doesn't change between calls to the JSON logger for an API call.
I left the two debug level logging statements that I used to troubleshoot as they may be helpful if a similar situation arises in the future.