Duplicate logs are created when logproxy runs into an error about logproxy HOT 2 CLOSED

After the latest update, we no longer see the duplicate logs. However, we're still missing log entries.
Thanks to the additional logging that logproxy now provides, I was able to capture a few log entries that result in an error, and an example of a log entry that is being forwarded.

I've captured three POSTs that resulted in an error:

While the response from HSP complains about the transactionId, that seems to be incorrect, as the transactionId is in the request and contains a UUIDv4 (which should be accepted by HSP Logging).

I've captured this example of a POST that was accepted:

Interestingly, this also contains a very similar transactionId, suggesting that that is indeed not the issue.
However, it also shows that in this example, the message is base64 encoded (which it was not in the previous examples).

Could it be that were running into two issues here?

• Logproxy not base64 encoding the message in some cases
• HSP Logging returning an incorrect error message in this scenario

from logproxy.

@RuudMeeuwsen looks like latest versions resolves this, closing. Thanks for the extensive issue details!

from logproxy.