Log header for rejecting message with too large header

The usage scenario I am thinking about; broker admins see many of these rejections but no way to trace it back to the application that is sending the offending message(s) to the broker. I have seen this scenario a few times, where broker admins had issues identifying which applications were responsible for these messages; so any data to help identify the offending message would be very useful.