MQ IPT Logging enhancements

Request to upgrade the connection logging in MQ IPT in order to make logs valuable and serchable for Splunk.
logging tools like Splunk prefers to have Key=Value pairs for values in order to index an entry/event
Key=Value pairs makes it possible to search for all that has happened to a route/port.

But IBM MQ IPT logs like this:

Sun Jan 14 05:53:57 CET 2024 conn nodata aaa.bbb.ccc(9482)     eee.fff.ggg.net(4125) OK       4125-2
Sun Jan 14 05:53:57 CET 2024 conn accept 10.11.12.13(1484)                  server.domain.net(5025) OK       5025-1
 

Which makes it impossible to know in Splunk what is source and what is destination.
 

I wish for following (or similar) syntax:

mqipt_datetime="2024-01-14T05:53:57.00" mqipt_msgid="MQCPIxxx" mqipt_type="conn" mqipt_event="nodata" mqipt_source="nodata aaa.bbb.ccc" mqipt_sourceport="9482" mqipt_dest="eee.fff.ggg.net" mqipt_destport="4125" mqipt_compl="OK" mqipt_thread="4125-2" mqipt_message=""

mqipt_datetime="2024-01-10T15:07:00.00" mqipt_msgid="MQCPIxxx" mqipt_type=conn" mqipt_event="close"  mqipt_source="127.0.0.1" mqipt_sourceport="4138"  mqipt_dest="127.0.0.1" mqipt_destport="7000" mqipt_compl="ERROR" mqipt_thread="7000-0" mqipt_message="Unrecognized SSL handshake request '54'"

Maybe include option to have log in JSON format like the mq error log
Maybe also include routename in log entries.

Also update console.log similar and with timestamp