RHDEVDOCS-2697

[rolfedh]

"do not configure the Log Forwarding API" statement is too general.
https://issues.redhat.com/browse/RHDEVDOCS-2697
[enterprise-4.6][enterprise-4.7][enterprise-4.8]

[netlify]

Deploy preview for osdocs ready!

Built with commit 51f7de6

https://deploy-preview-29671--osdocs.netlify.app

[jtudelag]

@rolfedh this is much more clear now, thanks!!

But I think there is room for clarification (avoid contrary statements), here it is mentioned as well:

If you want to forward all logs to only the internal OpenShift Container Platform Elasticsearch instance, do not configure the Log Forwarding API.

[rolfedh]

@rolfedh this is much more clear now, thanks!!

But I think there is room for clarification (avoid contrary statements), here it is mentioned as well:

If you want to forward all logs to only the internal OpenShift Container Platform Elasticsearch instance, do not configure the Log Forwarding API.

Thanks for spotting that one, too. Updated.

[ahardin-rh]

Just a few minor style suggestions from me! 👍

[rolfedh]

@anpingli Would you review and mark this "lgtm?" Thank you.

[anpingli]

/lgtm

[ahardin-rh]

/cherrypick enterprise-4.6

[ahardin-rh]

/cherrypick enterprise-4.7

[ahardin-rh]

/cherrypick enterprise-4.8

[openshift-cherrypick-robot]

@ahardin-rh: #29671 failed to apply on top of branch "enterprise-4.6":

Applying: [RHDEVDOCS-2697](https://issues.redhat.com/browse/RHDEVDOCS-2697) "do not configure the Log Forwarding API" statement is too general.
.git/rebase-apply/patch:57: trailing whitespace.
* `audit` - Logs generated by auditd, the node audit system, which are stored in the  */var/log/audit/audit.log* file, and the audit logs from the Kubernetes apiserver and the OpenShift apiserver. 
warning: 1 line adds whitespace errors.
Using index info to reconstruct a base tree...
M	logging/cluster-logging-external.adoc
M	logging/cluster-logging.adoc
M	modules/cluster-logging-collector-log-forwarding-about.adoc
M	modules/cluster-logging-manual-rollout-rolling.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/cluster-logging-manual-rollout-rolling.adoc
Auto-merging modules/cluster-logging-collector-log-forwarding-about.adoc
Auto-merging logging/cluster-logging.adoc
Auto-merging logging/cluster-logging-external.adoc
CONFLICT (content): Merge conflict in logging/cluster-logging-external.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 [RHDEVDOCS-2697](https://issues.redhat.com/browse/RHDEVDOCS-2697) "do not configure the Log Forwarding API" statement is too general.
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

Details

In response to this:

/cherrypick enterprise-4.6

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-cherrypick-robot]

@ahardin-rh: #29671 failed to apply on top of branch "enterprise-4.7":

Applying: [RHDEVDOCS-2697](https://issues.redhat.com/browse/RHDEVDOCS-2697) "do not configure the Log Forwarding API" statement is too general.
.git/rebase-apply/patch:57: trailing whitespace.
* `audit` - Logs generated by auditd, the node audit system, which are stored in the  */var/log/audit/audit.log* file, and the audit logs from the Kubernetes apiserver and the OpenShift apiserver. 
warning: 1 line adds whitespace errors.
Using index info to reconstruct a base tree...
M	logging/cluster-logging-external.adoc
M	logging/cluster-logging.adoc
M	modules/cluster-logging-manual-rollout-rolling.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/cluster-logging-manual-rollout-rolling.adoc
Auto-merging logging/cluster-logging.adoc
Auto-merging logging/cluster-logging-external.adoc
CONFLICT (content): Merge conflict in logging/cluster-logging-external.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 [RHDEVDOCS-2697](https://issues.redhat.com/browse/RHDEVDOCS-2697) "do not configure the Log Forwarding API" statement is too general.
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

Details

In response to this:

/cherrypick enterprise-4.7

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-cherrypick-robot]

@ahardin-rh: #29671 failed to apply on top of branch "enterprise-4.8":

Applying: [RHDEVDOCS-2697](https://issues.redhat.com/browse/RHDEVDOCS-2697) "do not configure the Log Forwarding API" statement is too general.
.git/rebase-apply/patch:57: trailing whitespace.
* `audit` - Logs generated by auditd, the node audit system, which are stored in the  */var/log/audit/audit.log* file, and the audit logs from the Kubernetes apiserver and the OpenShift apiserver. 
warning: 1 line adds whitespace errors.
Using index info to reconstruct a base tree...
M	logging/cluster-logging-external.adoc
M	logging/cluster-logging.adoc
M	modules/cluster-logging-manual-rollout-rolling.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/cluster-logging-manual-rollout-rolling.adoc
Auto-merging logging/cluster-logging.adoc
Auto-merging logging/cluster-logging-external.adoc
CONFLICT (content): Merge conflict in logging/cluster-logging-external.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 [RHDEVDOCS-2697](https://issues.redhat.com/browse/RHDEVDOCS-2697) "do not configure the Log Forwarding API" statement is too general.
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

Details

In response to this:

/cherrypick enterprise-4.8

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.