This is roughly what most of my Unix:Service events look like:
Mon Jul 15 12:33:46 PDT 2019 type=systemctl UNIT=wpa_supplicant.service, LOADED=loaded, ACTIVE=active, SUB=running, DESCRIPTION=WPA supplicant
But I'm seeing a fair number of events like this one:
Mon Jul 15 12:33:46 PDT 2019 type=systemctl UNIT=\x97\x8F, LOADED=systemd-vconsole-setup.service, ACTIVE=not-found, SUB=inactive, DESCRIPTION= systemd-vconsole-setup.service
It appears that there was some kind of data after the "type=systemctl" that has pushed the field values into the next field in line.
Anyone have any idea how to fix this?
Splunk... will you please stop spending development time on stupid things like Apple Watch apps and fix the Linux TA? It is severely broken and it is one of the most downloaded apps in the Splunkbase.
Upon further investigation, it would appear that the events get broken when systemctl outputs the value of the "load" column as "not-found".
So do you have a solution? Was it to upgrade or what?