The built-in fault engine is a bit restrictive but quite nice, it has error filtering, priority, and light-weight cross-loop communication built in.
Use the Set Fault VI to fire an error (pass the error information into the VI through the error cluster, don't bother filling in the source field and status fields, as they are ignored). Other than the error code, the only thing you have control over is the major fault control, which indicated whether this fault should be classified as major or minor. Note that the fault control can be overridden for certain errors based upon the fault configuration. Fault Configuration can be done with the fault configuration VIs or through the project, it primarily allows you to set the severity of the built-in scan engine errors, as well as establish occurrence thresholds for them and a few custom error codes.
To parse errors, call the Get Fault List VI. Note that it automatically filters faults and returns the number of times a fault has occured since it was last cleared as well as the timestamp of the first occurrance. In your case, I think the easiest thing to do would be to parse the fault list into a series of Syslog messages to transmit to your host program.
https://www.ni.com/en/support/downloads/tools-network/download.syslog-message-collector.html
That's a basic overview, feel free to ask if you have more detailed questions.
