diff --git a/guides/common/assembly_monitoring-hosts-by-using-red-hat-insights.adoc b/guides/common/assembly_monitoring-hosts-by-using-red-hat-insights.adoc index 28bef89071..662cea951c 100644 --- a/guides/common/assembly_monitoring-hosts-by-using-red-hat-insights.adoc +++ b/guides/common/assembly_monitoring-hosts-by-using-red-hat-insights.adoc @@ -6,7 +6,15 @@ endif::[] include::modules/ref_access-to-information-from-insights-in-project.adoc[leveloffset=+1] +// By default, Satellite sets "host_registration_insights" to true +// https://github.com/RedHatSatellite/foreman_theme_satellite/blob/develop/db/migrate/20201118090534_insights_param.rb +ifdef::satellite[] include::modules/proc_excluding-hosts-from-rh-cloud-and-insights-client-reports.adoc[leveloffset=+1] +endif::[] + +ifndef::satellite[] +include::modules/proc_enabling-rh-cloud-and-insights-client-reports-on-hosts.adoc[leveloffset=+1] +endif::[] include::modules/proc_deploying-red-hat-insights-by-using-the-ansible-role.adoc[leveloffset=+1] diff --git a/guides/common/modules/proc_enabling-rh-cloud-and-insights-client-reports-on-hosts.adoc b/guides/common/modules/proc_enabling-rh-cloud-and-insights-client-reports-on-hosts.adoc new file mode 100644 index 0000000000..53d8d0bfee --- /dev/null +++ b/guides/common/modules/proc_enabling-rh-cloud-and-insights-client-reports-on-hosts.adoc @@ -0,0 +1,20 @@ +[id="enabling-rh-cloud-and-insights-client-reports-on-hosts_{context}"] += Enabling RH Cloud and Insights client reports on hosts + +You can enable the Red Hat Insights client on hosts and have {Project} upload hosts inventory to the Insights service in the {RHCloud}. + +ifdef::katello,foreman-el,foreman-deb[] +Red Hat Insights is a service by Red Hat for {RHEL} hosts. +Ensure to set this parameter for {RHEL} hosts only. +If you set the parameter on any non-{RHEL} operating systems, {Project} automatically uploads new reports to the {RHCloud} when enabled in RH Cloud {Project} settings. +endif::[] + +.Procedure +. In the {ProjectWebUI}, navigate to *Host* > *Provisioning Setup* > *Operating Systems*. +. Select any {RHEL} operating systems for which you want to change the value. +. On the *Parameters* tab, add the `host_registration_insights` parameter, select the *boolean* type, and set the value to *True*. +. Click *Submit* to save the parameter. + +.Additional resources +* You can set this parameter at any level. +For more information, see {ProvisioningDocURL}Host_Parameter_Hierarchy_provisioning[Host parameter hierarchy] in _{ProvisioningDocTitle}_. diff --git a/guides/common/modules/proc_excluding-hosts-from-rh-cloud-and-insights-client-reports.adoc b/guides/common/modules/proc_excluding-hosts-from-rh-cloud-and-insights-client-reports.adoc index cf68c2153f..80a2d4ed03 100644 --- a/guides/common/modules/proc_excluding-hosts-from-rh-cloud-and-insights-client-reports.adoc +++ b/guides/common/modules/proc_excluding-hosts-from-rh-cloud-and-insights-client-reports.adoc @@ -4,16 +4,15 @@ You can set the `host_registration_insights` parameter to *False* to omit _rh-cloud_ and _insights-client_ reports. {Project} will exclude the hosts from _rh-cloud_ reports and block _insights-client_ from uploading a report to the cloud. -Use the following procedure to change the value of `host_registration_insights` parameter: - .Procedure . In the {ProjectWebUI}, navigate to *Host* > *All Hosts*. . Select any host for which you want to change the value. . On the *Parameters* tab, click on the edit button of `host_registration_insights`. . Set the value to *False*. -This parameter can also be set at the organization, hostgroup, subnet, and domain level. -Also, it automatically prevents new reports from being uploaded as long as they are associated with the entity. - If you set the parameter to false on a host that is already reported on the https://console.redhat.com/[Red Hat Hybrid Cloud Console], it will be still removed automatically from the inventory. However, this process can take some time to complete. + +.Additional resources +* You can set this parameter at any level. +For more information, see {ProvisioningDocURL}Host_Parameter_Hierarchy_provisioning[Host parameter hierarchy] in _{ProvisioningDocTitle}_.