Rsyslog message description

Rsyslog format is described in RFC3164 and RFC5424 documents, however this chapter described typical message format that comes from BS2000.

Typical messages that are visible on rsyslog server:

Oct 26 13:46:17 D017ZE40 SATT[5RTQ] evt="BDS" user-id="SYSWSA" res="S" applid="00c01040" connid="33000004" groupid="*UNI" 
ipv6own="FD5E:5E5E:0600:0000:0219:99FF:FE9C:7E8E" ipv6ptn="FD5E:5E5E:0600:0000:0000:0000:0000:0104" portown="8443" portptn="34642" rc="00000000"

that comes from BS2000 message:

<14>1 2023-10-26T13:46:17.57+02:00 D017ZE40 SATT 5RTQ SAT00180 [bs2000@231] evt="BDS" user-id="SYSWSA" res="S" applid="00c01040" connid="33000004" groupid="*UNI" 
ipv6own="FD5E:5E5E:0600:0000:0219:99FF:FE9C:7E8E" ipv6ptn="FD5E:5E5E:0600:0000:0000:0000:0000:0104" portown="8443" portptn="34642" rc="00000000"

The difference is due to extra information is used to filtering and sorting on rsyslog server.

Meaning of particular parts are described in diagram below:

Description of specific sections of the Header is detailed in RFC-5424.

SATCP event's fields and values are described in SATCP manual.

Event fields and values are written as a pair of field="value" separated by space. Particular value type are written as:

• c-strings are written as it is
• integers are written as string numbers
• x-strings are written as string consisting of hexadecimal numeric characters (0..9A..F)
• keywords are written as string (e.g. "STD", "YES", "SUCCESS", "NONE" etc.)