why sel-logger not add all info to journal?

[www]

Dear all,


Add sel-logger to openbmc project, when threshold sensor generate log, sel-logger will add message to journal, but why the message is incomplete?


sd_journal_send("MESSAGE=%s", message.c_str(),
                            "PRIORITY=%i", selPriority,
                            "MESSAGE_ID=%s", selMessageId,
                            "IPMI_SEL_RECORD_ID=%d", recordId,
                            "IPMI_SEL_RECORD_TYPE=%x", selSystemType,
                            "IPMI_SEL_GENERATOR_ID=%x", genId,
                            "IPMI_SEL_SENSOR_PATH=%s", path.c_str(),
                            "IPMI_SEL_EVENT_DIR=%x", assert,
                            "IPMI_SEL_DATA=%s", selDataStr,
                            NULL);
Sep 30 01:39:48 demoboard sel-logger[1187]: P12V sensor crossed a warning low threshold going low. Reading=0.089000 Threshold=11.400000.
Sep 30 01:39:48 demoboard sel-logger[1187]: P12V sensor crossed a critical low threshold going low. Reading=0.089000 Threshold=10.220000.
Sep 30 01:39:48 demoboard sel-logger[1187]: P5V sensor crossed a warning low threshold going low. Reading=0.231000 Threshold=4.750000.
Sep 30 01:39:48 demoboard sel-logger[1187]: P5V sensor crossed a critical low threshold going low. Reading=0.231000 Threshold=4.500000.
Sep 30 01:39:48 demoboard sel-logger[1187]: P3V3 sensor crossed a warning low threshold going low. Reading=0.002000 Threshold=3.100000.
Sep 30 01:39:48 demoboard sel-logger[1187]: P3V3 sensor crossed a critical low threshold going low. Reading=0.002000 Threshold=3.070000.
Sep 30 01:39:49 demoboard sel-logger[1187]: PVCCIN_CPU1 sensor crossed a warning low threshold going low. Reading=0.001000 Threshold=1.170000.
Sep 30 01:39:49 demoboard sel-logger[1187]: PVCCIN_CPU1 sensor crossed a critical low threshold going low. Reading=0.001000 Threshold=1.070000.
thanks,
Byron
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20191011/486ce2fe/attachment.htm>