Section Number and Name:
Describe the issue:
A customer used the steps provided in our docs and, by activating secure forwarding, this prevented internal elasticsearch from receiving the logs as well. The intention for the feature is to have the docs forwarded by the secure forwarding while also still collecting the logs in the internal elasticsearch. To resolve this, the customer added <store> </store> around the config, as follows:
@rich are you able to comment here?
Yes, this is correct. We need to fix this in the docs so customers will know to use the workaround. We also need to fix this in the code to add the <store></store> block either in secure-forward.conf, or in the fluentd.conf that includes this file.
Thanks for the information, all.
Rich, I've created a PR for this:
Can I please get an ack I've kept/removed the relevant information? The fox didn't have any certs info and I didn't want to presume.
Commit pushed to master at https://github.com/openshift/openshift-docs
Merge pull request #3744 from bfallonf/fluentd_1416223
Bug 1416223 fixed secure forwarding config in aggregating logging docs
Link to released docs: