Skip to content

Cherry-pick #21755 to 7.10: Increase recommended memory when deploying in Cloud foundry #21783

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 14, 2020
Merged

Cherry-pick #21755 to 7.10: Increase recommended memory when deploying in Cloud foundry #21783

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion deploy/cloudfoundry/filebeat/manifest.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
applications:
- name: filebeat
memory: 256M
memory: 512M
instances: 1
buildpacks:
- binary_buildpack
Expand Down
2 changes: 1 addition & 1 deletion deploy/cloudfoundry/metricbeat/manifest.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
applications:
- name: metricbeat
memory: 256M
memory: 512M
instances: 1
buildpacks:
- binary_buildpack
Expand Down
2 changes: 1 addition & 1 deletion filebeat/docs/running-on-cloudfoundry.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,7 +66,7 @@ To check the status, run:
$ cf apps

name requested state instances memory disk urls
filebeat started 1/1 256M 1G
filebeat started 1/1 512M 1G
------------------------------------------------

Log events should start flowing to Elasticsearch. The events are annotated with
Expand Down
2 changes: 1 addition & 1 deletion metricbeat/docs/running-on-cloudfoundry.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,7 +66,7 @@ To check the status, run:
$ cf apps

name requested state instances memory disk urls
metricbeat started 1/1 256M 1G
metricbeat started 1/1 512M 1G
------------------------------------------------

Metrics should start flowing to Elasticsearch. The events are annotated with
Expand Down