In this example message, the MSGID (ID42) is not extracted properly from the StructuredSyslogMessage:
<134>1 2025-11-18T10:28:07+0100 192.168.2.21 BIG-IP 42 ID42 - client_ip="10.0.0.139" target_ip="192.168.3.21" srcPort=26807 dstPort=443 proto="TCP" action="accept" info="blablabla"
It seems the MSGID is only extracted if the message contains structured content. If no [ exists in the message, no further parsing is happening. However, only in the parsing of the structured message, the MSGID is extracted.
In this example message, the
MSGID(ID42) is not extracted properly from theStructuredSyslogMessage:It seems the MSGID is only extracted if the message contains structured content. If no
[exists in the message, no further parsing is happening. However, only in the parsing of the structured message, the MSGID is extracted.