1.proposed title of this feature request

syslog integration support for octet-counted framing,

2. Who is the customer behind the request?

     Account: Public Health England(5258190)

     TAM customer: no

     CSM customer: no

     Strategic: no

3. What is the nature and description of the request?

~~~

It seems that non-transparent framing is the only framing method supported by the syslog integration. This is documented in RFC 6587 "Transmission of Syslog Messages over TCP" section 3.4.2. The RFC also documents octet-counted framing, which is the only reliable way to tell the syslog server how long messages are so that they are not truncated, can embed newlines, etc. This is documented in section 3.4.1 of the RFC. The RFC that specifies how syslog messages should be sent over TLS, RFC 5425 "Transport Layer Security (TLS) Transport Mapping for Syslog" describes only the octet-counted framing method, in section 4.3.1. Nonetheless, there are plenty of syslog servers that do implement the non-standard non-transparent framing method. Is it possible to have the below integration ,

Can syslog integration expose an option, "framing method" that can be set to "octet-counted" or "non-transparent", so that messages transferred via plaintext TCP, as well as messages transferred via TLS, can be sent to syslog servers that support either framing method.

~~~

4. Why does the customer need this? (List the business requirements here)

Avoid multiple lines in message

5. How would the customer like to achieve this? (List the functional requirements here)

getting the required function in the RHACS

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

syslog using doc (https://docs.openshift.com/acs/3.69/integration/integrate-using-)syslog-protocol.html

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?

NO

8. Does the customer have any specific time-line dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?

NA

9. Is the sales team involved in this request and do they have any additional input?

NA

10. List any affected packages or components.

NA

11. Would the customer be able to assist in testing this functionality if implemented?

NA