Cherry-pick #17275 to 7.7: Add documentation for deploying filebeat and metricbeat in Cloud Foundry. #17299
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry-pick of PR #17275 to 7.7 branch. Original message:
What does this PR do?
Adds documentation on running filebeat and metricbeat inside of Cloud Foundry.
Why is it important?
Because almost all operators of Cloud Foundry will want to deploy it inside of the foundation.
Checklist
I have commented my code, particularly in hard-to-understand areasI have added tests that prove my fix is effective or that my feature worksCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.How to test this PR locally
Follow the instructions to ensure it results in a running filebeat and metricbeat inside of Cloud Foundry.
Related issues