anchor.diff:  +
   ----
   secure-forward.conf: |
  -  # <store>
  +  # <store> 
     # @type secure_forward
   
     # self_hostname ${hostname}
  
positive.code: // Module included in the following assemblies:
  //
  // * logging/cluster-logging-collector.adoc
  
  [id="cluster-logging-collector-external_{context}"]
  = Configuring Fluentd to send logs to an external log aggregator
  
  You can configure Fluentd to send a copy of its logs to an external log
  aggregator, and not the default Elasticsearch, using the `secure-forward`
  plug-in. From there, you can further process log records after the locally
  hosted Fluentd has processed them.
  
  ifdef::openshift-origin[]
  The `secure-forward` plug-in is provided with the Fluentd image as of v1.4.0.
  endif::openshift-origin[]
  
  ////
  ifdef::openshift-enterprise[]
  The `secure-forward` plug-in is supported by Fluentd only.
  endif::openshift-enterprise[]
  ////
  ////
  [NOTE]
  ====
  For Rsyslog, you can edit the Rsyslog configmap to add support for Syslog log forwarding using the *omfwd* module, see link:https://www.rsyslog.com/doc/v8-stable/configuration/modules/omfwd.html[omfwd: syslog Forwarding Output Module]. To send logs to a different Rsyslog instance, you can use the *omrelp* module, see link:https://www.rsyslog.com/doc/v8-stable/configuration/modules/omrelp.html[omrelp: RELP Output Module].
  ====
  ////
  
  The logging deployment provides a `secure-forward.conf` section in the Fluentd configmap
  for configuring the external aggregator:
  
  .Procedure
  
  
negative.code:   # </server>
    # </store>
  ----
  ////
  