Add documentation for deploying filebeat and metricbeat in Cloud Foundry. #17275
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
blakerouse
changed the title
|
Pinging @elastic/integrations-platforms (Team:Platforms) |
exekias
approved these changes
Mar 27, 2020
exekias
added
docs
needs_backport
bvader
reviewed
Mar 27, 2020
|
@bvader I don't know about standard in that case, but the yaml anchors are fully supported by the yaml parsing module used by beats and it makes updating the configuration a lot simpler. In this case I think its worth it. |
4 tasks
blakerouse
added
v7.8.0
and removed
needs_backport
4 tasks
blakerouse
added a commit
to blakerouse/beats
that referenced
this pull request
Mar 31, 2020
…dry. (elastic#17275) * Add running-on-cloudfoundry for filebeat. * Fix typo. * Add running on cloudfoundry for metricbeat. * Add changelog. * Add missing newline at end of metricbeat manifest. * Fix filebeat being referenced in metricbeat docs. (cherry picked from commit 850d1fa)
blakerouse
added a commit
to blakerouse/beats
that referenced
this pull request
Apr 3, 2020
…dry. (elastic#17275) * Add running-on-cloudfoundry for filebeat. * Fix typo. * Add running on cloudfoundry for metricbeat. * Add changelog. * Add missing newline at end of metricbeat manifest. * Fix filebeat being referenced in metricbeat docs. (cherry picked from commit 850d1fa)
leweafan
pushed a commit
to leweafan/beats
that referenced
this pull request
Apr 28, 2023
…dry. (elastic#17275) (elastic#17299) * Add running-on-cloudfoundry for filebeat. * Fix typo. * Add running on cloudfoundry for metricbeat. * Add changelog. * Add missing newline at end of metricbeat manifest. * Fix filebeat being referenced in metricbeat docs. (cherry picked from commit e29d929)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
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.asciidocorCHANGELOG-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