Merge pull request #143 from infrawatch/lmadsen-tweaks

A few tips

Author: JoanneOFlynn2018

doc-Service-Telemetry-Framework/modules/proc_preparing-your-openshift-environment-for-stf.adoc

@@ -71,6 +71,8 @@ The amount of resources that you require to run {ProjectShort} depends on your e
 
 {ProjectShort} uses ElasticSearch to store events, which requires a larger than normal `vm.max_map_count`. The `vm.max_map_count` value is set by default in {OpenShift}.
 
+TIP: If your host platform is a typical {OpenShift} 4 environment, do not make any adjustments. The default node tuning operator is configured to account for ElasticSearch workloads.
+
 If you want to edit the value of `vm.max_map_count`, you cannot apply node tuning manually using the `sysctl` command because {OpenShift} manages nodes directly. To configure values and apply them to the infrastructure, you must use the node tuning operator. For more information, see https://docs.openshift.com/container-platform/{SupportedOpenShiftVersion}/scalability_and_performance/using-node-tuning-operator.html[Using the Node Tuning Operator].
 
 In an {OpenShiftShort} deployment, the default node tuning operator specification provides the required profiles for ElasticSearch workloads or pods scheduled on nodes. To view the default cluster node tuning specification, run the following command:

doc-Service-Telemetry-Framework/modules/proc_validating-clientside-installation.adoc

@@ -26,6 +26,8 @@
 
 To validate data collection from the {ProjectShort} storage domain, query the data sources for delivered data. To validate individual nodes in the {OpenStack} deployment, connect to the console using SSH.
 
+TIP: Some telemetry data is only available when {OpenStack} has active workloads.
+
 .Procedure
 
 . Log in to an overcloud node, for example, controller-0.