<134>Jan 12 16:18:59 worker0 fluentd: I0112 16:18:57.831175 1763 setters.go:77] Using node IP: "192.168.200.13"
=> The fixed "fluentd" string is printed in every log message. So customers can not identify which daemon printed this message.

<134>Jan 12 16:18:59 worker0 hyperkube[1763]: I0112 16:18:57.831175 1763 setters.go:77] Using node IP: "192.168.200.13"
=> The daemon name should be included in every log message.

1. Deploy ClusterLogging with "clusterlogging.openshift.io/logforwardingtechpreview: enabled"
2. Prepare an external syslog server
3. Apply the following config map on openshift-logging, then check if the external syslog server receives messages from ClusterLogging

    ---
    kind: ConfigMap
    apiVersion: v1
    metadata:
      name: syslog
      namespace: openshift-logging
    data:
      syslog.conf: |
        <store>
         @type syslog_buffered
         remote_syslog 192.168.122.1  
         port 514
         hostname rhocp4
         remove_tag_prefix tag
         tag_key ident,systemd.u.SYSLOG_IDENTIFIER
         facility local0
         severity debug
         use_record true
         payload_key message
        </store>
    ---
4. Apply the following LogForwarding object
    ---
    apiVersion: logging.openshift.io/v1alpha1
    kind: LogForwarding
    metadata:
      name: instance
    spec:
      disableDefaultForwarding: true
      outputs:
        - name: user-created-es
          type: elasticsearch
          endpoint: elasticsearch.openshift-logging.svc:9200
          secret:
            name: fluentd
      pipelines:
        - name: app-pipeline
          inputSource: logs.app
          outputRefs:
            - user-created-es
        - name: infra-pipeline
          inputSource: logs.infra
          outputRefs:
            - user-created-es
        - name: audit-pipeline
          inputSource: logs.audit
          outputRefs:
            - user-created-es
    ---
5. Check if external syslog server receives messages with daemon names from ClusterLogging