Chapter 5. How to select the right data collection tool

To display data about your subscription usage, subscription watch requires a data collection tool to obtain that data. The various data collection tools each have distinguishing characteristics that determine their effectiveness in a particular type of environment.

It is possible that the demands of your environment require more than one of the data collection tools to be running. When more than one data collection tool is supplying data to the services in the Cloud Services platform, the tools that process this data are able to analyze and deduplicate the information from the various data collection tools into standardized facts, or canonical facts.

The following information can help you determine the best data collection tool or tools for your environment.

5.1. Red Hat Insights

Insights as a data collection tool is ideal for the always-connected customer. If you fit this profile, you are interested in using Insights not only as a data collection tool, but also as a solution that provides analytic, threat identification, remediation, and reporting capabilities.

With the inclusion of Insights with every Red Hat Enterprise Linux subscription beginning with version 8, and with Insights available as an operator with Red Hat OpenShift Container Platform beginning with version 4.2, the use of Insights as your data collection tool becomes even more convenient.

However, using Insights as the data collection tool is not ideal if the Insights agent cannot connect directly to the cloud.redhat.com website or if Red Hat Satellite cannot be used as a proxy for that connection. In addition, it cannot be used as the sole solution if hypervisor host-guest mapping is required for virtual data centers (VDCs). In that case, Insights must be used in conjunction with Satellite.

5.2. Red Hat Subscription Management

Red Hat Subscription Management is an ideal data collection tool for the connected customer who uses the Subscription Manager agent to send data to Red Hat Subscription Management on the Red Hat Customer Portal.

For customers that are using subscription watch, Red Hat Subscription Management automatically synchronizes its data with the Cloud Services platform tools. Therefore, in situations where Red Hat Subscription Management is in use, or required, such as with RHEL 7 or later, it is being used as a data collection tool.

5.3. Red Hat Satellite

The use of Satellite as the data collection tool is useful for customers who have specific needs in their environment that either inhibit or prohibit the use of the Insights agent or the Subscription Manager agent for data collection.

For example, you might be able to connect to the Cloud Services platform directly, but also have a need to use Satellite to maintain accurate hypervisor host-guest mapping information for a virtual data center (VDC) subscription. In that case, you might find the connection and maintenance of a per-organization Satellite installation is more convenient than the per-system installation of Insights. The use of Satellite also enables you to inspect the information that is being sent to the Cloud Services platform on an organization-wide basis instead of a system-only basis.

As another example, your Satellite installation might not be able to connect directly to the Cloud Services platform because you are running Satellite from a disconnected network. In that case, you must export the Satellite reports to a connected system and then upload that data to the Cloud Services platform. To do this, you must use a minimum of Satellite 6.5 or later. You must also install the Satellite inventory upload plugin on your Satellite server.

5.4. Red Hat OpenShift

Subscription watch is designed to work with customers who use Red Hat OpenShift 4.1 and later in connected environments. Customers with disconnected Red Hat OpenShift Container Platform environments can use Red Hat OpenShift as a data collection tool by manually creating each cluster in Red Hat OpenShift Cluster Manager. This workaround enables customers with disconnected environments to simulate an account-level view of their Red Hat OpenShift usage. For example, an organization with disconnected clusters distributed across several departments might find this workaround useful.

The data collection for Red Hat OpenShift 4.1 and later usage is dependent on several tools, including tools developed by the Red Hat OpenShift development team. For Red Hat OpenShift Container Platform version 4.1 and later, the Prometheus and Telemetry tools in the monitoring stack and Red Hat OpenShift Cluster Manager are used to gather and process cluster data before sending it to Red Hat Subscription Management. Red Hat Subscription Management provides the relevant usage data to the Cloud Services platform tools such as inventory and subscription watch.

For Red Hat OpenShift Container Platform version 3.11, data collection is dependent on an older, Red Hat Enterprise Linux based reporting model. Therefore, data collection is dependent upon the connection of the Red Hat Enterprise Linux nodes to one of the Red Hat Enterprise Linux data collection tools, such as Insights, Red Hat Subscription Management, or Satellite.

Additional resources

  • For additional help with deciding which data collection tool or tools to use, see the Red Hat Subscription Watch Helper. This Red Hat Customer Portal Labs application is available at https://access.redhat.com/labs/rhsw/. The application guides you through a series of questions to determine the data collection tools that are the best fit for your environment.