IMPORTANT ANNOUNCEMENT: On May 6, 2024, Carbon Black User eXchange (UeX) and Case Management will move to a new platform!
The Community will be in read-only mode starting April 19th, 7:00 AM PDT. Check out the blog post!
You will still be able to use the case portal to create and interact with your support cases until the transition, view more information here!

BSD syslog format (RFC 3164) for Cb Response

BSD syslog format (RFC 3164) for Cb Response

The cool thing about Cb Response is, you can make SYSLOG messages be literally any format you want, standard or non-standard.  Altering the basic format is done by making edits to /etc/rsyslog.d/cb-coreservices.conf.  Altering the contents of the "msg" parameter involves changes to templates in "/usr/share/cb/rsyslog".  All this is documented, per the information in Chapter 5, in our "Cb Response Integration Guide" at https://community.carbonblack.com/docs/DOC-6708.

Specifically for BSD syslog format (per RFC 3164), if you need support for that, do the following:

(RFC 3164 format is not related to what's in the "msg" part of the SYSLOG transmission.  It has to do more with the so-called "headers."  So you just need to edit cb-coreservices.conf.  You don't have to mess around with the templates.)

  1. Find the line that starts with
      $template CbSyslogStandardFormatWithPID
  2. Create a new line below it that looks like this:
      $template CbSyslogRFC3164Format,"%timegenerated% %source% %programname%[%procid%]: %msg%\n"
  3. Now, in all the lines down below that start with "if $programname", wherever you see the string "CbSyslogStandardFormatWithPID", replace it with  "CbSyslogRFC3164Format".  Make sure it's only that one string you replace.  It does not occur on all the lines, only some.

You may need to restart the "rsyslogd" process for the changes to take effect.

Labels (1)
Tags (1)
Was this article helpful? Yes No
No ratings
Article Information
Author:
Creation Date:
‎05-12-2017
Views:
1389
Contributors