Skip to content
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.

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

Issue #810 Document resource requirements for alerting, telemetry #1056

Merged
merged 1 commit into from Mar 2, 2020

Conversation

kowen-rh
Copy link
Contributor

@kowen-rh kowen-rh commented Mar 2, 2020

No description provided.

@@ -8,6 +8,9 @@ One of these is Prometheus and all the related monitoring, alerting, and telemet

* A running {prod} virtual machine and a working [command]`oc` command.
For more information, see <<accessing-the-openshift-cluster-with-oc_{context}>>.
* Additional memory assigned to the {prod} virtual machine.
At least 12 GiB of memory is recommended.
For more information, see <<configuring-the-virtual-machine_{context}>>.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@robin-owen Additional memory need to be assigned to the {prod} virtual machine ? the current sentence seems like, it automatic assigned :)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated and also added that the value for 12 GiB of memory is 12288. Let's not make people do math if they don't have to. ;)

@@ -8,6 +8,9 @@ One of these is Prometheus and all the related monitoring, alerting, and telemet

* A running {prod} virtual machine and a working [command]`oc` command.
For more information, see <<accessing-the-openshift-cluster-with-oc_{context}>>.
* You must assign additional memory to the {prod} virtual machine.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants