anchor.diff:  * `audit`. Audit logs generated by the node audit system, `auditd`, Kubernetes API server, OpenShift API server, and OVN network.
   --
   +
  -You can add labels to outbound log messages by using `key:value` pairs in the pipeline. For example, you might add a label to messages that are forwarded to others data centers or label the logs by type. Labels that are added to objects are also forwarded with the log message.
  +You can add labels to outbound log messages by using `key:value` pairs in the pipeline. For example, you might add a label to messages that are forwarded to other data centers or label the logs by type. Labels that are added to objects are also forwarded with the log message.
   
  -* An _input_ forwards the application logs associated with a specific project to a pipeline.
  +_input_:: Forwards the application logs associated with a specific project to a pipeline.
  ++
  +--
  +In the pipeline, you define which log types to forward using an `inputRef` parameter and where to forward the logs to using an `outputRef` parameter.
  +--
  ++
   
  -In the pipeline, you define which log types to forward using an `inputRef` parameter and where to forward the logs to using an `outputRef` parameter.
  +_Secret_:: A `key:value map` that contains confidential data such as user credentials.
   
   Note the following:
   
  
positive.code: * You can use multiple types of outputs in the `ClusterLogForwarder` custom resource (CR) to send logs to servers that support different protocols.
  
  * The internal {product-title} Elasticsearch instance does not provide secure storage for audit logs. We recommend you ensure that the system to which you forward audit logs is compliant with your organizational and governmental regulations and is properly secured. OpenShift Logging does not comply with those regulations.
  
  * You are responsible for creating and maintaining any additional configurations that external destinations might require, such as keys and secrets, service accounts, port openings, or global proxy configuration.
  
  The following example forwards the audit logs to a secure external Elasticsearch instance, the infrastructure logs to an insecure external Elasticsearch instance, the application logs to a Kafka broker, and the application logs from the `my-apps-logs` project to the internal Elasticsearch instance.
  
  
negative.code: == Fluentd log handling when the external log aggregator is unavailable
  
  If your external logging aggregator becomes unavailable and cannot receive logs, Fluentd continues to collect logs and stores them in a buffer. When the log aggregator becomes available, log forwarding resumes, including the buffered logs. If the buffer fills completely, Fluentd stops collecting logs. {product-title} rotates the logs and deletes them. You cannot adjust the buffer size or add a persistent volume claim (PVC) to the Fluentd daemon set or pods.
  
  [discrete]
  == Supported Authorization Keys
  Common key types are provided here. Some output types support additional specialized keys, documented with the output-specific configuration field. All secret keys are optional. Enable the security features you want by setting the relevant keys. You are responsible for creating and maintaining any additional configurations that external destinations might require, such as keys and secrets, service accounts, port openings, or global proxy configuration. Open Shift Logging will not attempt to verify a mismatch between authorization combinations.
  
  Transport Layer Security (TLS):: Using a TLS URL ('http://...' or 'ssl://...') without a Secret enables basic TLS server-side authentication. Additional TLS features are enabled by including a Secret and setting the following optional fields:
  
  * `tls.crt`: (string) File name containing a client certificate. Enables mutual authentication. Requires `tls.key`.
  
  * `tls.key`: (string) File name containing the private key to unlock the client certificate. Requires `tls.crt`.
  
  * `passphrase`: (string) Passphrase to decode an encoded TLS private key. Requires `tls.key`.
  
  * `ca-bundle.crt`: (string) File name of a customer CA for server authentication.
  
  Username and Password::
  * `username`: (string) Authentication user name. Requires `password`.
  * `password`: (string) Authentication password. Requires `username`.
  
  Simple Authentication Security Layer (SASL)::
  * `sasl.enable` (boolean) Explicitly enable or disable SASL.
  If missing, SASL is automatically enabled when any of the other `sasl.` keys are set.
  * `sasl.mechanisms`: (array) List of allowed SASL mechanism names.
  If missing or empty, the system defaults are used.
  * `sasl.allow-insecure`: (boolean) Allow mechanisms that send clear-text passwords. Defaults to false.
  